Viewing environments
Deployer provides a way to register and keep track of your environments(servers) that you want to deploy to.
Every environment has a status icon that shows if it is available for deployment. An environment can only be deployed to if it is enabled and has a status of active
. A status of active
means that Deployer has recently been able to connect to the environment (see below for more details).
When viewing an environment you can:
- See the status of the environment. Each environment can be in one of the following states:
waiting
Deployer is currently waiting for an initial connection from the environment. This usually means that the environment has not yet been configured to use Deployeractive
Deployer currently has a constant connection with the environment, each couple of minutes.timeout
Deployer has been able to connect to the environment previously, however there have been no recent successful connections. This indicates that there may be a problem with your environment or the Deployer settings in Integrations Hub. TheLast connection
field will indicate how long ago the last successful connection was.
- The package version, along with the Jadu CMS and Jadu XFP versions, that are currently running on the environment
- How long ago a successful connection with your environment was last established. Usually this will update at 10 minute intervals.
- Name
- Url
- Patch Memory Limit (MB) is the maximum allowed memory for patching process. Setting this value too low might may cause patches to fail. Setting it too high may impact performance of the website. Minimum value is 64M. This feature is available from version 1.5.0 of the integration package on your environment
- If the environment is enabled or not
- If the environment is protected or not. A protected environment can't have development packages deployed to it. Mark the important environments like LIVE or UAT as marked to prevent experimental CMS versions and features from being patched to them.
- Connection key. A unique connection key that needs to be configured in the Deployer settings with the Integrations Hub of your environment.