# bricks install

Deploy a blueprint to a selected collection

## Synopsis

Deploy a blueprint to a selected collection

```
bricks install [blueprint] [flags]
```

## Examples

```

  bricks install @bluebricks/postgres --collection=production --props-file=path/to/props.json
```

## Options

```
  -c, --collection string      Collection slug as the environment target (alias: --col)
      --env-slug string        Environment slug (alias: --slug)
  -f, --file string            Path to a YAML manifest file (bricks/v1 schema) that defines the deployment non-interactively
      --plan-only              Will create a deployment plan only
  -p, --props string           JSON string containing blueprint properties i.e '{"collection": "dev"}'
      --props-file string      Path to JSON file containing blueprint configuration properties. Cannot be used with --props or --file
      --set-slug string        Set environment slug
      --template-file string   Path to a template file that generates one or more deployment manifests
      --values-file string     Path to a YAML values file to use with the template file
  -y, --yes                    Automatically consent to the planning, direct deploy
```

## Options inherited from parent commands

```
      --api-key string    API key for authentication (overrides JWT)
      --config string     config file (default is $HOME/.bricks/config.yaml)
  -h, --help              Print Help message for Bricks CLI
      --non-interactive   Suppresses interactive UI elements for non-interactive environments
  -v, --version           Print bricks CLI version
```

## SEE ALSO

* [bricks](https://github.com/bluebricks-dev/Bluebricks-Documentation/blob/main/cli-reference/bricks.md) -