The 5.7 branch of Magnolia reached End-of-Life on December 31, 2023, as specified in our End-of-life policy. This means the 5.7 branch is no longer maintained or supported. Please upgrade to the latest Magnolia release. By upgrading, you will get the latest release of Magnolia featuring significant improvements to the author and developer experience. For a successful upgrade, please consult our Magnolia 6.2 documentation. If you need help, please contact info@magnolia-cms.com.

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