• By rmescandon
  • Latest version (#0)
  • xenial, trusty
  • Stable


Cronify delivers a single cron.d file and a payload for executing scheduled


Cron.d file contents

To encode the cron.d file:

$ base64 -w 0 my-cron-file

Then use the contents as the value for the 'cron_data' option.
A quick way to set this would be

$ juju set cron/0 cron_data=$(base64 -w 0 my-cron-file)

Payload contents

Create a file named payload.tgz and add bundle it with the charm under


(string) The target path for the $CHARM_DIR/files/payload.tgz contents
(string) The status of service-affecting packages will be set to this value in the dpkg database. Valid values are "install" and "hold".
(string) Space separated list of extra deb packages to install.
(string) A base64 encoded string containing the contents of the cron.d file.
(string) List of signing keys for install_sources package sources, per charmhelpers standard format (a yaml list of strings encoded as a string). The keys should be the full ASCII armoured GPG public keys. While GPG key ids are also supported and looked up on a keyserver, operators should be aware that this mechanism is insecure. null can be used if a standard package signing key is used that will already be installed on the machine, and for PPA sources where the package signing key is securely retrieved from Launchpad.
(string) List of extra apt sources, per charm-helpers standard format (a yaml list of strings encoded as a string). Each source may be either a line that can be added directly to sources.list(5), or in the form ppa:<user>/<ppa-name> for adding Personal Package Archives, or a distribution component to enable.
(string) The name of the cron.d file.