Magnolia Cloud updates 2020
This page lists the updates for Magnolia Cloud in 2020.
November
Magnolia 6.2.5
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.
Magnolia 6.2.4
With this update, you can use Magnolia CMS 6.2.4 when setting up your environments in the cloud.
Release notes for Magnolia CMS 6.2.4 are available.
September
Magnolia 6.2.3
With this update, you can use Magnolia CMS 6.2.3 when setting up your environments in the cloud.
Release notes for Magnolia CMS 6.2.3 are available.
August
Using Datadog’s Metric Explorer to create custom reports
You can now use Datadog’s Metric Explorer to filter reports. For more information, see Monitoring and logging.
Tearing down Environments
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.
Subscriber Management Improvements
You now receive confirmation of adding and deleting subscribers in the Cockpit for an even better user experience. For more information, see Managing subscribers.
Improved redirect process in the Cockpit
The redirect process in the Cockpit has been simplified. For more, see Configuring domain redirect rules.
Third party updates
The following third-party libraries have been updated to fix security and compatibility issues:
-
Tomcat updated to 9.0.37
We keep the details of the security-related fixes private in line with our security policy. Contact our Support team if you need more information.
July
Magnolia 6.2.2
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.
Hiding custom bundle snapshots in the Cockpit
You can now hide custom bundle snapshots in the Cockpit when setting up a new environment or upgrading. For more on this, see Hiding custom bundle snapshots.
Managing subscribers from the Cockpit
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.
June
Global accelerator service
Magnolia has rolled out the AWS Global Accelerator service for all our cloud subscription packages. What this means for you:
-
Better response times for your live instances.
-
Simplified domains and certificate management.
May
Magnolia 6.2.1
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.
Magnolia Cloud magnolia.properties file conventions
Applies to _custom cloud bundle implementations only.
From Magnolia 6.2.1, Magnolia provides a cloud-specific option in the Magnolia Maven Archetype to facilitate the creation of your cloud bundles.
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
NOTE:
-
Two default profiles are generated:
devandshared. These profiles have their ownmagnolia.propertiesfiles. -
During packaging, the
devprofile is excluded. Thesharedprofile 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. -
In the
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
March
Magnolia 6.2 (LTS release)
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. |
Self-service deployment of Java customizations
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
-
Upgrade anytime
This service is available for customers with a custom cloud bundle.
Global presence
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
-
Enhanced compliance
-
Costs optimization
The region for your deployment should be discussed with Magnolia before your project starts. The region cannot be modified after Magnolia is already deployed.
Magnolia 6.1.5
With this update, you can use Magnolia CMS 6.1.5 when setting up your environments in the cloud.
February
Magnolia 5.7.6 and 6.1.4
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.