Packages
A package represents a deployable application or content. It contains URIs, properties, and configuration data that help define how the application is constructed and deployed. To deploy a package, you create an instance that represents a version of this content, with its referenced URI content fetched and stored in the database. Storing this information ensures that the application version is protected from any external influences.
References
A reference represents a link to the content (file, directory, archive, etc.) which you use for the deployment process. To deploy a package you need to create in it at least one reference. Package without reference cannot be deployed.
Dependencies
Package references and repository content are associated with a dependency tree. This tree dictates the deployment order for the content.
Specify dependencies to:
- Deploy the content of an instance in a particular order
- Deploy multiple pieces of instance content at the same time
Analyzers
Analyzers identify modules that break down fetched content. They are invoked after a URI has been fetched into the package instance. You configure analyzers to perform specific actions.
Analyzers are associated with references in a package. When an associated reference is fetched, the analyzers are run to further process it. You can assign multiple analyzers in a certain order to a given reference to create a processing chain of events. For more information and a list of available analyzers, see Using-analyzers.
Automatic name generation for instances
The name generated for an instance can contain automatically created values, such as a number that automatically increases for each instance constructed or values that represent the time and date that the instance was created. You can specify where to use these automatic values.
Related topic