File Uploads

As part of Corus 4.0, the ability to deploy arbitrary files to Corus has been introduced. This feature is meant as a convenience, whereby the distributed management facility of Corus can be used to deploy files across multiple hosts at once.

When files are deployed in such a manner, Corus makes no attempt to determine what these files are about (it will not attempt, for example, that such a deployed file may consist of a Corus application distribution).

By default, such files are kept under the $CORUS_HOME/files/uploads directory. This location is configurable, by modifying the corus.server.uploads.dir in the corus.properties configuration file (itself under $CORUS_HOME/config directory).

Deploying Files

To deploy a file, simply type the deploy command in the CLI, together with the -f option, whose value should be set to the path of the file to deploy.

deploy -f myArchive.zip

The -cluster option works its magic for this command also, triggering the deployment of the file across all hosts in the cluster:

deploy -f myArchive.zip -cluster

In addition the, the command also takes a -d option. The option can be used to provide a user-defined directory where the file is to be uploaded on the Corus node:

deploy -f myArchive.zip -d /opt/uploads

Listing Deployed Files

To list the currently deployed files, use the ls command with the -f option:

ls -f -cluster

Note that this will only list the files present under Corus' uploads directory. If you have deployed files with the -d option set to another directory, it will not be magically remembered by Corus.

Undeploying Files

To undeploy, just use undeploy, with the -f option also. Here are examples:

undeploy -f myArchive.zip
undeploy -f myArchive.zip -cluster
undeploy -f *.zip

Similarly to the ls command, the files deployed to user-defined directories will not be seen by Corus, and thus you will not be able to undeploy files from under such directories.