Page Comparison

...

bm client deploy <path to local project>

For example, to deploy the contents of the current folder:

bm client deploy .

Once deployed, your changes will be instantly available at your project URL.

...

 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.

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.

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.

bm client deploy --force

--skip

The "skip" option will bypass unchanged files (default) on your local machine.

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.

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.

bm client deploy <path to local project> --prune--prune

--debug

The "debug" option will display extra debugging information. This is useful if you are having issues deploying your web app.

bm client deploy --debug

Using Multiple Environments (Dev, Test, Prod): 

Anchor
multipleEnvironmentsHeading multipleEnvironmentsHeading

...