For this you have the bootstrap process and the version handlers. But it's a looooong topic. Very shortly said: - You export what you need as XML (e.g. page, component and dialog definitions, site definitions, themes and if you want even sample data, although we usually don't put these under version control). - Then you add these XMLs to the mgnl-bootstrap folders of your Magnolia module project (src/main/resources/mgnl-bootstrap/[module-name] - And like this, you have the data under version control (as it is part of your project folder)
At this point, anyone who does a clean install will have the data bootstrapped. However in most cases you don't want to constantly do a clean install (because you might have test data etc. in your repositories that you don't want to be wiped away). This is where the version handler comes into play. There you can tell what exactly should be bootstrapped, added, modified, deleted you name it between version X and Y. Have a look at the version handlers of some of the modules to get an idea. Not the easiest of things to do, but [b]very[/b] helpful, if done right! -will -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=dacbff3f-0ce9-4293-b8b2-b5c1843568b7 ---------------------------------------------------------------- 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: <[email protected]> ----------------------------------------------------------------
