Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.

To enable bootstrapping in light modules install the Content Importer module.

This page provides an overview of how bootstrapping works in light modules. Please also see Content Importer module which provides more detail on the subject.

Bootstrap files are used to load content into the JCR. Bootstrap files make it easier to share content across Magnolia instances. In light modules bootstrap files are typically used to load content such as pages, assets and others.

How bootstrapping in light modules works

  1. Export JCR data from Magnolia's AdminCentral.
  2. Place the exported files in the bootstrap folder on the file system of a running Magnolia instance. See Setting the bootstrap directory.
  3. When Magnolia detects a change in the bootstrap directory it sends a task to the Pulse.
  4. superuser assigns himself the task and imports the content into the corresponding workspace in the JCR. 

See How content import works for a more detailed explanation.

Bootstrap files can also be imported or bootstrapped manually using the import actions in the JCR Browser and many other apps. However, the content of this page is limited to importing bootstrap files in the Pulse and the term "bootstrapping" is used in this context only.

Using bootstrap files

Things to note about bootstrap files:

  • Bootstrap files are only detected on a running Magnolia instance. The bootstrap directory is not observed on startup. Add your bootstraps after starting Magnolia. 
  • Deletions are not removed automatically. To remove content, delete it in the JCR and the bootstrap directory.
  • superuser permissions are required to import content in the Pulse.

  • No labels