The lifecycle environments page can be accessed via The Content Menu:
Content > Lifecycle Environments
The lifecycle environments page forms a part of orcharhino’s content management. (See also: Content Management Guide).
A lifecycle environment exists to regulate host access to a particular version of some given content view. (See also: Content Views).
Lifecycle environments are organized into so called lifecycle environment paths. Each path may consist in one or more lifecycle environments.
It is in principle possible to create any number of lifecycle environment paths, consisting in any number of arbitrarily named lifecycle environments. It is also possible to completely forego the use of lifecycle environment paths by limiting yourself entirely to the default Library environment. (Which always exists on every orcharhino installation).
However, for the sake of explaining orcharhino’s lifecycle management this documentation presumes a standard use case. In particular, we will use a single lifecycle environment path composed of three lifecycle environments as follows:
Development > Testing > Production
This brings us to a total of four lifecycle environments when the default Library environment is included.
The basic idea of orcharhino’s lifecycle management is to place each host (or host group) into a single lifecycle environment based on role. For example a host used by the development department would be placed in the Development environment. Since developers are expected to be working on the newest version of some software, we might then assign the newest version of some orcharhino content view (see also: Content Views) to the Development environment. The development hosts would then have access to the newest version of the software in the content view. At the same time hosts in the Production environment might still be using a much older (tested and stable) version of the same content view. By promoting new software versions through the lifecycle environment path in a step-by-step fashion, we ensure new versions are tested and stable by the time they are pushed into the Production environment.
Even organizations that do not develop their own software might never the less wish to test new software in a limited environment, before pushing it onto their production servers. By default, the Library environment will include the latest version of every content view.