3.6.1. Deploying Bundles

3.6.1. Deploying Bundles
Prev	3.6. Deployments	Next

The deploy command is used to deploy a bundle from inventory into an environment. For a loadable bundle, this deployment is just a reference to the original bundle (a file inside the environment's 'uses' directory containing a path to the original bundle). For an executable bundle, this deployment is a separate directory containing a bundle reference and a work directory for the bundle's runtime files.

The deploy command takes an optional name parameter, which allows you to choose a name for the deployment that is different from the bundle name. This allows mutiple instances of a bundle to be deployed within the same deployment, provided each is given a unique name. This can be useful for setting up a application cluster.

BundleWorks calls a different bundle hook depending on whether a deployment already exists in the target environment.

If the deployment does not exist, the bundle hook 'install' is executed.
If the deployment exists and the existing bundle is older, the bundle hook 'upgrade' is executed.
If the deployment exists and the existing bundle is newer, the bundle hook 'rollback' is executed.

BundleWorks used the 'Created-Date' attribute inside the bundle info file to determine whether a bundle is older or newer.