Skip to content

Terms Used in This Section

These are the terms used across Managing Changes to a Live Compatibility Package and its pages.

Note: See Alchemy Glossary for Alchemy terminology in general.

Term What it means
The application The software itself: the thing your users open and use.
The base package The master, undeployed copy of the Compatibility Package, held wherever you keep it, usually a network share. This is the copy you deploy from, and the copy every future deployment is made from. Also called the package folder or the source copy.
The deployed copy What deployment creates on an individual machine from the base package. There is one deployed copy per machine, and each was made from the base package as it stood at the time.
Deployment The act of putting the Compatibility Package onto a machine so users can run it. Done by running the deployment program in the base package.
ProgData The folder inside the Compatibility Package that holds the application's own files. Its contents mirror the paths the application occupies on a normal installation. This is the part of the Compatibility Package you can change.
The package root The top level of the Compatibility Package: the .xml and .clc configuration files and the Cloudhouse programs. This part cannot be changed. See Package Structure and Locations.
The container The isolated environment the application runs inside on the machine. It is what allows the application to run on an operating system it was never designed for. "Container" is also used loosely as another name for the Compatibility Package itself; these pages use it only in the first sense.
Package version The version of the Compatibility Package, recorded inside the Compatibility Package itself. This is not the same as the version of the application inside it. See Rolling Back a Change.

Related Pages