Add a bundle to a specified path to make it available for deployment into an environment.
bw add ARCHIVE PATH
- ARCHIVE is either a path to a local file or a URL to a remote file.
- ARCHIVE must point to a tar-gzip or zip archive containing a valid bundle.
- PATH can be any writable directory.
<bw.add archive="${archive}" path="${path}" />
# Add apache bundle archive to /opt/bundles
bw add apache-2.2.6.tgz /opt/bundles
# Add bundle from url to 'bundles' inside home directory
bw add http://dev.example.com/downloads/hello-1.5.zip ~/bundles
- This command will not replace an existing bundle of the same name and version. You need to use bw remove to remove the existing bundle first.
- During the 'add', the 'setup' bundle hook is executed.
- During the 'add', BundleWorks sets all items in a bundle to 'read-only'. If your bundle requires different permissions, use a 'setup' bundle hook.
- If you are using a URL to access a bundle, you must protect the resource from unauthorized access. One possibility is to use IP or host-based restrictions.