Environment creation is automated and takes only a couple of minutes. You can deploy the following environments:
Any Jahia DX module can be deployed on these environments.
When you create an environment, you only need to provide the following parameters:
Creating a new environment takes between 5 and 10 minutes, depending on the complexity and size of the platform. When you start creating the environment, Jahia Cloud displays a loading screen until the environment is ready for use.
Environment upgrades are fully automated and follow the typical Jahia upgrade path, meaning that an environment can only be upgraded to the next immediate version.
The upgrade service upgrades environments without generating any downtime for the end visitor. The service also changes the content-contribution mode to read-only mode for a few minutes.
For an environment that is not in production, the upgrade service:
To perform a zero-downtime environment upgrade in production:
As a best practice, before upgrading your production environment Jahia recommends:
For each software upgrade that contains significant changes (indicated by the first two digits in Jahia version numbers), we release code migration guides to make the code upgrade process as easy as possible. If in doubt, don't hesitate to reach out to our support team for guidance.
You can use the backup service in two different ways:
All backups are stored in secure storage, protected by credentials that are only available to you through your Jahia Cloud account or to our support teams. The environment backups contain everything related to code (modules) and content and ensure that the restored environment will behave exactly as the original one. Backups are stored for an unlimited amount of time and are deleted when your backup quota is reached. The default quota is set to 30 environment snapshots and can be increased for a fee.
A scheduled or on-demand snapshot does not generate downtime for end visitors to your site. However, the platform will change to read-only mode while the snapshots occurs to ensure data consistency.
The backup and restore service displays a list of all backups available for a specific environment. Restoring a backup installs a new platform following the same process as for creating an environment.
Load balancers are automatically installed for each new environment. These load balancers are composed on nginx servers and a layer of automation ensures that we do not redirect traffic to a server that is not available. Load balancers enable you to restart any node on a cluster without generating downtime and to deploy configuration to a cluster one server after another.
If no nodes are available to answer visitors page and API requests, a Jahia page indicates that the requested website is in maintenance.
Even though cluster features and environment creation are managed automatically by Jahia Cloud, you can perform actions on specific Jahia DX Manager servers. Available actions for each node include:
Jahia DX Manager comes with great built-in code deployment capabilities and allows for cluster module deployment from APIs or file upload. To learn more, see Jahia module deployment explained.
There is no restriction whatsoever on the type of modules, and built-in and custom integrations that you can deploy on Jahia Cloud.
Jahia Cloud offers a fully dedicated environment. This means that you get as much liberty to configure your cloud environment as if it were hosted on-premise. You configure your environment in a user interface that provides explanations about configuration options, and insights about the right configuration for specific use cases.
After validating the environment configuration, you must restart application nodes to apply the configuration changes. Nodes can be restarted one-by-one without generating any downtime as dynamic load balancers stop sending traffic to nodes that are restarting.