Deployment

Deployments form another fundamental component of CloudNet. Unlike Templates, deployments do not copy files to services. They represent the opposite direction. A deployment allows files from services to be copied back to a configured template after stopping.

Template

The Template setting allows you to determine which template the files of a service should be copied back to. This means specifically that by executing the deployment, the files of the service are copied to the specified template.

Excludes

The Excludes setting allows you to exclude individual files or folders based on RegEx expressions. The excluded files and folders are not copied back to the template.

If you want, for example, the logs folder not to be copied, the exclusion could look like this:

"excludes": [
  "logs/"
]

By default, the following two excludes are set for deployments. The reason for this is to prevent outdated CloudNet files from being reused.

"wrapper\\.jar",
"\\.wrapper/"

These should not be removed from the excludes.

Includes

The Includes setting allows you to include individual files or folders based on RegEx expressions. By setting includes, other files are no longer copied back to the template and only the explicitly included files and folders are copied.

If you want, for example, only the plugins folder to be copied, the inclusion could look like this:

"includes": [
  "plugins/*"
]

Properties

The Properties setting allows you to add any kind of JSON structure to a deployment. By default, CloudNet does not use these properties. Modules and plugins can use these properties for their own advanced functions.