The Magnolia cockpit is the central point of access to all functionality provided by Magnolia in the cloud. This page gives you a brief overview of the main screens in the cockpit and what actions can be performed.
Actions started in the cockpit are executed sequentially.
There is an action queue per Magnolia subscription package.
You cannot trigger an action before the action started before has finished being executed.
A URL for the cockpit and login details for all the users you requested are provided by Magnolia when you subscribe to Magnolia's cloud offering. Use this information to access the cockpit.
Once you have logged in, you can manage your user settings by clicking on your name in the top right corner.
You are logged out automatically after 30 minutes of inactivity for security reasons.
Welcome! The first page you will see upon logging in is the subscription packages page. It shows the package created for you by Magnolia and its status.
From this page, you can:
- View your package and its current status. Click on the status icon to see details about the status of the package.
- Click Show package overview to access the package overview.
Click Show package overview in the subscription packages page to access the package overview page. This page is the access point for all the package administration actions for the cloud-based cloud Magnolia.
From this page you:
- Access the activity log
- Manage your environments
- Install updates
- View a list of stakeholders
- View additional information about the GIT repository linked to the subscription package.
The activity log displays a log of all major actions triggered from the cockpit providing a single location to see who did what when.
A Magnolia package typically consists of three environments:
- Live - Where the tested and approved version of the content product is delivered to customers.
- UAT (User Acceptance Testing) - Where the next version of the product is made available to editors and managers for testing and review.
- Integration - Where developers try out ideas and test solutions before giving internal users access.
As features are developed, the configuration is tested and moved from Integration, through UAT and finally to Live.
From the environments section, you can:
- Troubleshoot your package using logs
- Set up a new environment - If no environment of a given type exists, you can directly create one. If one already exists, you have to tear down the existing one before.
- Manage environments - Access actions to change your setup:
Each environment consists of one or several spaces , which separate the environment into larger blocks containing public or author instances of Magnolia. By default each environment has an Author space and a Public space.
For a given environment, you can:
- View default site - View the public instance of the site, which must be named home.
- Edit content - Access the author instance of the package to edit content.
You can also hover your cursor over the version number displayed to see information about the release currently installed.
Commit timestamp or Installation timestamp (when followed by the text "Installed on").
Commit ID - Shown if the commit has no tag defined.
Commit tag - Shown if a tag is defined for the commit.
The package overview page provides information about what has been installed in your package in the Installed releases section.
You can view time stamped releases and install updates.
The Install an update page is the access point for developers to retrieve their work and propagate it thought the different environments and testing stages before putting it into production.
See the following pages for information about how to:
- Install a development snapshot
- Define a new release
- Copy content for testing
- Change the version of Magnolia
The package overview page displays a list of stakeholders and their contact details in the People section.
The GIT repository associated to the subscription package is displayed in the Additional information section of the package overview page.
When you develop locally, you must push your configuration changes to this GIT repository so they can be installed in the Integration environment.