To deploy you your client code and assets to the Client project area, you can use the deploy command.:
| Code Block | ||
|---|---|---|
| ||
bm client deploy <path to local project> |
...
| Info |
|---|
|
For example, to deploy the contents of the current folder:
| Code Block | ||
|---|---|---|
| ||
bm client deploy . |
...
Once deployed, your changes will be instantly available at your project URL.
| Info |
|---|
|
...
| Tip |
|---|
| By default, your project will be deployed to the "dev" environment: company-project-dev.blinkm.io. You can deploy to a different environment using the --env tag as described below. |
Additional Options
--env (default to dev)
This allows you to set the environment you wish to deploy to, such as dev, test, or prod. See the "Using Multiple Environments" section for more details.
| Code Block | ||||
|---|---|---|---|---|
| ||||
bm client deploy <path to local project> --env prod |
--skip
The "skip" option will bypass unchanged files (default) on your local machine.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
bm client deploy <path to local project> --prune |
Using Multiple Environments (Dev, Test, Prod):
| Anchor | ||||
|---|---|---|---|---|
|
This service allows you to deploy to multiple environments for your project, using the "env" option.
Environments are specified in the API URL as a dash followed by the environment name.
For example, by default, the dev environment is used:
https://company-project-dev.blinkm.io
If, however, you were to set "--env test" option, your API URL would be:
https://company-project-test.blinkm.io
Production URLs:
While any environment name can be used, "prod" is treated a little differently. Production URLs don't use the environment dash; instead it will produce as a shorter, cleaner API URL.
So in this case, "--env prod" will produce the API URL:
https://company-project.blinkm.io