This page lists the updates for Magnolia Cloud in 2019. Click on an entry to see details or Expand/Collapse All .
Cloud bundle variants
Magnolia has adjusted its cloud offer to better suit the needs of our customers and partners.
Standard bundle – Light Development
This cloud variant focuses on speed and agility for your projects. Your site is hosted in Magnolia Cloud; Magnolia manages the environment as a service.
The fully managed environment provides the infrastructure for Light Development as well as the Cockpit, which you use for:
- Deployment workflow
- Backup and restore
- Logs and Monitoring
- Additional services
With this cloud variant you can customize Magnolia using light development and manage the deployment environment via the Cockpit. This variant includes the standard DX Core bundle and additionally offers Magnolia Connector Packs and selected Special Features (see supported modules).
Custom bundle – Light Development and Java Development
This cloud variant is geared toward complex projects that need a high level of customization. With this cloud variant you can customize Magnolia using both Light Development and Java custom modules.
Your site is hosted in Magnolia Cloud and you or your chosen Partner manages the creation of custom Java modules and the deployment of the bundle. This variant provides the highest level of flexibility allowing for a custom CMS that fits your unique needs. It also includes all the functionality of the standard DX Core bundle and additionally offers Magnolia Connector Packs and selected Special Features (see supported modules).
Our experienced Services team is available to provide best practices and help you on board to our cloud.
With custom bundles, our customers and partners may not deploy configuration that results in creating a secondary repository.
Should this happen, workspaces and content stored in anything other than a Magnolia-provided repository is not included in:
- Backup operations.
- Content cloning operations.
- SLA obligations.
You can see the bundle types that can be used in your subscription package in the Additional Information section.
More information displayed for environments and bundles
When you hover over the environment branch or tag icon in the Environments section in the cockpit, you now see a creation timestamp for the snapshot or release installed in addition to the existing information.
When setting up or upgrading an environment, instead of just the bundle version, you also have the full bundle name displayed.
Installing a snapshot on UAT or Live
Depending on your project requirements, your subscription package environments may vary and affect the standard development cycle.
If your subscription package does not include an integration environment, you can install a development snapshot directly in the UAT environment.
If your package only consists of a Live environment (no integration or UAT), you can also install a development snapshot in the Live environment.
For more information, see Installing a snapshot.
Magnolia CMS 6.1
Release notes for Magnolia CMS 6.1 are available.
Note that the Contacts, Synchronization, Link Mapper and jsonfn modules are no longer included in the cloud bundle as they are not part of DX Core. See Product packaging in the 6.1 release notes for more information.
When an environment is protected, a green shield icon is displayed next to it in the Package overview. You must disable protection (using the same cockpit wizard) to be able to tear down the environment again.
For more information, see Protecting environments.
With this update, you can use Magnolia CORE 5.7.3 when setting up your environments in the cloud. Note that 5.7.3 is a bug-fixing and security release.
Release notes for Magnolia CORE 5.7.3 are available.
We recommend that Magnolia CORE 5.7.3 be used for your production environments until the release of Magnolia CMS 6.1
Restart your instances in the cloud
You can restart instances one by one using a wizard in the cloud cockpit.
For more information, see Restarting instances.
View information about your database
You can view the Allocated storage space and Free storage space for the database linked to your cloud-based Magnolia package in the cockpit.
For more information, see Viewing cloud database information.
Domain name changes
Previously, Magnolia required definitive domain names to be provided during the onboarding process. Now you can add and remove domain names and manage certificates at any time by contacting the Magnolia Cloud Helpdesk.
Upgrade backups are automatically removed
When you upgrade your Live environment from one version of Magnolia to another, an automatic upgrade backup is created for rollback purposes. This backup is now automatically removed after 48h. If you require the backup to be kept for a longer period of time if, for example, you have encountered issues or need additional time to validate the upgrade, you can extend the time period from 48 hours to 5 days.
Until the automatic backup is removed, you cannot tear down your upgraded environment. If you need to tear down the environment, you can delete the upgrade backup manually.
Environment setup wizard supports multiple runtimes of bundles
When you set up an environment, you now see runtime information (the OS, JDK and Tomcat versions) when selecting a bundle.
Previously only the bundle type and version were displayed.
6.0.1 cloud pack bundle released to fix multisite licensing issue
Due to a licensing issue in Magnolia 6.0, cloud customers were unable to use the Multisite module functionality. We have released a 6.0.1 cloud pack bundle to resolve this issue. Please upgrade your cloud pack bundle version of Magnolia if you require multisite.
Support for Git branches when installing a snapshot
When moving your development work from Git to your Cloud subscription package, you can now select which Git branch you want to retrieve content from. Previously only the latest commit or a tagged version was available from the Master branch, obliging you to squash and rebase your work before moving it to Magnolia Cloud.
Being able to select a Git branch means you can apply a simple code change to a specific environment without deploying any other (possibly half-finished) code that might already be in your repository. For example, you can hot fix your live environment without affecting ongoing testing on the UAT environment.