Magnolia Cloud updates 2020
This page lists the updates for Magnolia Cloud in 2020.
With this update, you can use Magnolia CMS 6.2.5 when setting up your environments in the cloud.
Release notes for Magnolia CMS 6.2.5 are available.
You can now use Datadog’s Metric Explorer to filter reports. For more information, see Monitoring and logging.
When tearing down a Live environment, your public IPs are lost. You receive a notification in the Cockpit confirming that you know the IPs will be lost. For more information, see Tearing down an environment.
You now receive confirmation of adding and deleting subscribers in the Cockpit for an even better user experience. For more information, see Managing subscribers.
The redirect process in the Cockpit has been simplified. For more, see Configuring domain redirect rules.
With this update, you can use Magnolia CMS 6.2.2 when setting up your environments in the cloud.
Release notes for Magnolia CMS 6.2.2 are available.
A new user group has been added to the Cockpit called Subscribers. This is in addition to Owners, Developers, and Magnolia Support. Subscribers do not have access to the Cockpit, but receive email notifications as set by your Subscription. For more on this, see Managing subscribers.
With this update, you can use Magnolia CMS 6.2.1 when setting up your environments in the cloud.
We urge all cloud customers to upgrade their projects to use the latest Magnolia LTS release within 60 days of the version release date. All new deployments must be based on the latest LTS version of Magnolia.
Release notes for Magnolia CMS 6.2.1 are available.
Applies to _custom cloud bundle implementations only.
The Magnolia Maven Archetype generates a best-practice project skeleton. The Magnolia Cloud Maven Plugin validates and uploads your custom cloud bundle.
my-mgnl-cloud-webapp/ ├── pom.xml └── src └── main └── webapp └── WEB-INF └── config └── dev │ └── README.md │ └── magnolia.properties └── shared └── README.md └── magnolia.properties
Two default profiles are generated:
shared. These profiles have their own
During packaging, the
devprofile is excluded. The
sharedprofile is included and deployed to Magnolia Cloud.
You can add local developer credentials to the
devprofile to be used instead of the typical Magnolia superuser/superuser, which is disabled in the cloud.
sharedprofile, you can create specific
.propertiesfiles for each cloud environment. This can be used, for example, to test the integration of a third-party tool in the UAT environment without affecting your Live environment.
Make sure you use the latest version of the Magnolia Cloud Maven Plugin when deploying a new bundle to Magnolia Cloud: v1.0-RC6.
If you previously created a custom bundle with
More information can be found in the readme here: README
With this update, you can use Magnolia CMS 6.2 when setting up your environments in the cloud.
Release notes for Magnolia CMS 6.2 are available.
|Magnolia 6.2 is an LTS release.|
Magnolia Cloud now supports self-service deployment of Java customizations. As a cloud customer, you or your chosen partner can deploy your custom Java code via our cloud self-service platform.
Streamlined and reduced deployment cycle
This service is available for customers with a custom cloud bundle.
Previously all Magnolia deployments were based in Frankfurt where our main hosting center is. Now we have the possibility to deploy to other locations based on your project requirements. This offers:
Lowest latency possible for best customer experience
The region for your deployment should be discussed with Magnolia before your project starts. The region cannot be modified after Magnolia is already deployed.
With this update, you can use Magnolia CORE 5.7.6 and Magnolia CMS 6.1.4 when setting up your environments in the cloud.