Message-ID: <346840883.9629.1406528777875.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_9628_275882908.1406528777874" ------=_Part_9628_275882908.1406528777874 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
An existing configuration plugs itself onto an existing container instal= lation that exists on your hard disk. This is by opposition to the Standalone Local Configu= ration which creates a new container installation from scratch in a dir= ectory of your choice. Existing configurations require that the user create= s a valid configuration directory and points Cargo to it.
Whenever you configure or start a container which uses an existing confi= guration, Cargo will:
As a result, Cargo will not be configuring the configuration properties nor the data sources and resources<= /a> on your container; these need to be configured beforehand.
Please note that this method does not guarantee reproducibility, as the = configuration is not "cleaned" at any point. If you want to keep = a generated configuration you can ask Cargo to generate a standalone configuration once = and then consider it an .
There are different ways of using an existing configuration:
DefaultConfigurationFactorywhich automatical= ly maps the right implementation for the container you're using. For exampl= e: