...
| Code Block |
|---|
|
bm client deploy <path to local project> --env prod--env prod |
--cwd (defaults to current folder)
This allows you to set the current working directory for your deployment. By default, it will use the current directory.
| Code Block |
|---|
|
bm client deploy --cwd ./myfolder |
--force
This will deploy your project without asking for confirmation. This feature is designed to allow automatic deployments for those interested in an automated release.
| Code Block |
|---|
|
bm client deploy --force |
--skip
The "skip" option will bypass unchanged files (default) on your local machine.
| Code Block |
|---|
|
bm client deploy <path to local project> --skip |
--no-skip
The "no-skip" option will upload all files, including unchanged files on your local machine.
| Code Block |
|---|
|
bm client deploy <path to local project> --no-skip |
--prune
The "prune" option will remove any files that don't exist on your local machine.
| Code Block |
|---|
|
bm client deploy <path to local project> --prune |
--debug
The "debug" option will display extra debugging information. This is useful if you are having issues deploying your web app.
| Code Block |
|---|
|
bm client deploy <path to local project> --debug |
Using Multiple Environments (Dev, Test, Prod):
| Anchor |
|---|
| multipleEnvironmentsHeading |
|---|
| multipleEnvironmentsHeading |
|---|
|
...