Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Cargo Daemon is a Web-based application that uses the Cargo API to configure, start and stop containers on a remote machine. The daemon is meant to be listening 24/7, to allow users to deploy new containers and web applications at their command. For more information, please read: Cargo Daemon.

Note
titleContainer configuration for the Daemon

For the Maven2/Maven3 plugin, the "daemonized server" is actually a local container with a hostname that points to a remote machine. This implies that:

  • You should not set the container type to a remote container nor add any remote deployers to the configuration; but instead define the container as a local container (with either a standalone or existing configuration)
  • When you define the home paths for the container and the configuration, remember these paths are remote (and, preferably, use absolute paths)

When you call the cargo:daemon-start, the Maven2/Maven3 plugin will do the following:

  • If an installer is defined:
    • Download the archive locally
    • Send the archive over to the machine running the Daemon
    • Instruct the Daemon to extract the archive
  • If a standalone local configuration is defined, instruct the Daemon to create it
  • In all cases, send the configuration files and deployables to the machine running the Daemon and instruct the Daemon to deploy them
  • Instruct the Daemon to start the container

<daemon> elements

Description

Mandatory?

Default value

<classpaths>

A list of <classpath>myclasspath</classpath> items, that will be added by the JVM launcher when starting a container.

(thumbs down)

No default

<properties>

A list of properties used to configure the Cargo Daemon.

(thumbs up)

No default

...