Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Definition

Specifies how the container is configured

Explanation

A Configuration specifies how the container is configured (logging, security, data sources, location where to put deployables, etc).

Configuration != Installation

Icon

The notion of Configuration is different from the notion of Installation. When you install a container, it is usually configured by default too to start and deploy files from where it is installed. However all containers support customizing the configuration and even possibly use a different location where the configuration resides.



There are 2 main types of Configurations:

Configuration features

Custom configuration

(TODO: update the section below as it's no longer exact)

The Cargo API allows you to plug your own custom configuration implementation. The only requisites is that the implementation must implement ContainerConfiguration and have a CustomConfiguration(URI home) constructor (for local containers, home is the URI pointing to directory from where to start the container; for remote containers, home is the URI required to manipulate the container).

You can then register your configuration against the DefaultConfigurationFactory class. It's optional and only required if you want to let users use the DefaultConfigurationFactory class to instantiate your configuration. You would write:

Where new ConfigurationType("customhint") is to create a type of configuration, used to differentiate your configuration from other existing ones associated with the container represented by its id. You could of course implement an existing type such as ConfigurationType.STANDALONE or ConfigurationType.EXISTING.

  • No labels