Description

Juju charm for deploying content to Apache

How to deploy the charm

Use this charm as a subordinate to a charm like apache2. It will download the
content and install it on the server.

This charm can be joined to a remote-content relation if the superordinate
needs to take action after content is updated. If no action is needed it can
be joined to the generic juju-info relation. If remote-content is used then
the superordinate can set the dest_dir

Supported sources

Currently swift, bzr+ssh, file, lp, http, https and ftp are supported. http,
https and ftp access can either be anonymous or via a username and
password. bzr+ssh requires a private key to be shipped with the charm, this
should be a private key which is used for nothing else. swift requires the
full gamut of authentication information.

dest_dir is the location to expand the archive into. In the case of apache
this would most likely be the document root specified in the vhost

keep_dir_count is the number of backups of the deployed content to keep.
Before each deploy the current content is archived before the new content is
pulled in.

By default any change to the charm state ie upgrade-charm or config-changed
will trigger the content update process to run. This behaviour can be changed
by setting update_on_change to false in which case deploy_trigger is used
to trigger a deploy of new content and should be incremented to trigger a
deploy. Note that when update_on_change is false setting any other
parameter will not trigger a deployment.