[magnolia-dev] [JIRA] (SUGGEST-70) Improve bootstrapping in light modules

[JIRA (on behalf of Ondrej Chytil)]

Title: Message Title

Ondrej Chytil created an issue   Suggestion Box / SUGGEST-70 Improve bootstrapping in light modules Issue Type: Improvement Assignee: Unassigned Created: 17/Jan/17 11:41 AM Priority: Neutral Reporter: Ondrej Chytil Right now the only way to bootstrap content via the light module is to drop the xml files into observed directory of a running instance. We should add a functionality to bootstrap a content upon startup of an instance so make the light modules bootstrap functionality similar to the regular Maven module bootstrapping. This would make light modules handier because right now there's no way how to distribute a content along with the light module. If there is any content, the devs have to either copy the light module into the Maven module or separate at least the bootstrapped content into the Maven module. So the front end devs are forced to work with the regular modules anyway (we wanted to avoid that by introducing the light modules). Implementation suggestion: Light module will contain a folder (mgnl-bootstrap), this folder will contain 4 subfolders named based on ImportUUIDBehavior. Placing the bootstrap file into one of these folder will determine the way how the bootstrap files will be handled (remove, replace...). Bootstrap will then happen just like in case of any Maven module, so respecting the installation order if there's any dependency in the light module descriptor. Bootstrap files might be accessible via the Resources app. They should be editable as regular resources, plus an action to execute the bootstrap/import should be available in the app. This can be useful if there's a need to revert a content to it's original state. This might even be extended to Maven modules' bootstrap files. Bootstrap folders should be visible to superuser role only. After the bootstrapping is done we have to ensure that xml files won't be bootstrapped again on the next startup. For this purpose an entry stating what was bootstrapped the last time should be saved somewhere. One possibility is to create a yaml file on the FS where the files will be listed with true/false so re-bootstrapping is possible by the config. This file would be loaded in Resources app as well. The other option is to save this info somewhere in the repository (probably resources workspace) from where it will be loaded by the Definitions app, similar as we load the app/template etc. definitions. Optionally there might be a separate app for the functionality regarding bootstrapping. Add Comment   This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------