Page tree
Skip to end of metadata
Go to start of metadata
 What are my options for managing error pages?

Currently, only the responses for the HTTP 404 code can be customized in the Magnolia Cloud. You can customize the response by creating a "404" page in the Pages app, under your main page. 
Then in the Configuration app -> /server/webContainerResources/mappings@docroot, change the value of that property from "/docroot/*" to "/modules/*".
Finally, create a Virtual URI mapping for forwarding the requests to your new "404" page:

 I have my own custom-built Magnolia module that I previously used in an on-premises implementation, can I use it in the cloud as well?

Only light modules can be used in Magnolia cloud. If you have a custom-built Java module you would like to use in the cloud, please contact our Help Desk for evaluation and guidance.

 I have broken my integration/UAT/Live environment, what should I do now?

In the case of the Live environment:

  1. Set up a new Live environment.
  2. Install the release to recover any Magnolia light modules you added.
  3. Restore from backup to recover any custom configuration and content.

 In the case of an integration or UAT environment:

  1. Set up a new environment.
  2. Install a snapshot in the integration environment or Install the release in UAT to recover any Magnolia light modules you added.
  3. Copy content from the Live environment if required.
 Someone deleted content (page, asset) and I need to restore it. How can I do that?
  • In the case of content in the Live environment: restore from backup to recover any custom configuration and content. This will restore the deleted content.
  • In the case of content in the Integration or UAT environments: copy content from the Live environment. This will restore the deleted content.
 Someone deleted the entire site, what should I do now?

In the case of the Live environment:

  1. Set up a new Live environment.
  2. Install the release to recover any Magnolia light modules you added.
  3. Restore from backup to recover any custom configuration and content.

 In the case of an integration or UAT environment:

  1. Set up a new environment.
  2. Install a snapshot in the integration environment or Install the release in UAT to recover any Magnolia light modules you added.
  3. Copy content from the Live environment if required.
 All my light modules have been deleted, how can I get them back?
  • In the case of the Live environment: install the release to recover any Magnolia light modules you lost.
  • In the case of the UAT environment: install the release in UAT to recover any Magnolia light modules you lost.
  • In the case of the Integration environment: install the snapshot with the Magnolia light modules to recover them.
 I heard the CLI can make it easier for me to develop with Magnolia. Can I use the Magnolia CLI in the cloud and how?

Yes, you can use the CLI to develop locally and then add that development work to Magnolia Cloud. 

The Magnolia CLI speeds up creating and developing light modules. The tool includes commands to install and start Magnolia, and to create modules, pages and components.

Follow the Hello-cloud - a development tutorial that makes use of Magnolia CLI to learn how it works.

 I made some changes to my light module and broke the rendering of pages in production, how can I fix it?

Install the previous site release to recover the Magnolia light modules you previously added.

 How can I add or remove users from Magnolia Cloud?

There are two types of user account:

 How is my data stored in Magnolia Cloud?

Live data is stored in Amazon RDS (based on PostrgeSQL). Backups are fully managed by RDS.

 I've run into an issue in the cloud, how can I report it?
 I want to access a service on my premises from magnolia instances and I need to whitelist its IP addresses

We currently assign Elastic IPs (ie: static IPs) to Author and Public instances of each client. These instances will keep the addresses even on new deployments, but if the installation grows or is downscaled, the assigned IPs might be changed, in such case the client should be informed again of the new IP addresses (by Magnolia or the client's initiative, this is part of the scaling process).

  • No labels