Page History
This page gives an overview of an overview of the complete Magnolia development cycle :for standard and custom bundles.
| Table of Contents | ||
|---|---|---|
|
Standard cloud bundle development workflow
| Include Page | ||||
|---|---|---|---|---|
|
Standard Cloud bundle development workflow
Local development
Creating new features and functions in your Magnolia package starts with local development. After cloning the remote Git repository linked to your Magnolia subscription package, you install a Magnolia local development bundle on your machine. This is where you develop new features before sending them to the cloud via the Git repository.
...
| Anchor | ||||
|---|---|---|---|---|
|
Working in Magnolia cloud
After developing locally and pushing your work to the Magnolia Git repository, log in to the cockpit to retrieve your work. As well as providing an overview of your package's status, the cockpit is the starting point for all the actions you can do in Magnolia in the cloud:
- Install updates using Magnolia - Create development snapshots and releases to deploy and test new features through the different environments in Magnolia before making your site available to your customers.
Continuous delivery is a way to ensure that new configuration, templates and code can be rapidly and safely deployed to production. You deliver every change first to a UAT environment and verify that business applications and services function as expected through testing. Since every change is delivered to the UAT environment using automation in the Magnolia Cloud Cockpit, you have confidence that the application can be deployed to the Live environment exactly the same way, with a push of a button when the business is ready. In the UAT environment, business users can validate your changes with real content cloned from the Live environment.
Adapted from Caum, Carl: Continuous Delivery Vs. Continuous Deployment: What's the Diff?
- Manage environments in Magnolia - Create and manage the environments and running instances of Magnolia in the cloud.
...
| Bestpractice |
|---|
Magnolia recommends that you develop your light module files using Magnolia CLI. If you want to use it, you have to install it. Magnolia light modules can nonetheless also be developed without using Magnolia CLI. |
See Setting up a local Git repository to get started with your standard bundle development workflow.
...
Hands-on learning
Try out our end-to-end Hello -cloud Cloud development tutorial, in which you set up a light module and deploy it in Magnolia.
...
Overview
Content Tools