Hi Matteo, Perhaps we can work together on this? I have a module that is working on magnolia 4.4, and need to port it to magnolia 5.
It already does the following: - export to JCR content to file-system - uses "syndication" like logic to collect the nodes comprising a "unit of content" into one exported file - uses a line-oriented text format rather than JCR system view XML (XML is not mergable, text format is) - exports templates (freemarker), resource content and dms (documents) as separate files rather than inline in JCR content - compares JCR and existing output to find differences - visualizes differences for text files in side-by-side diff view - configurable export "packages" --> you can configure different (sub-)trees in magnolia to be exported to different file system locations (thus you could configure an export for all the data needed for a site: theme, resources, templates, definitions and dms content to a single file-system location). Open points: - It currently has a UI based on a magnolia page. It would have to be changed to use Vaadin and an App. - It currently uses magnolia 4.4 formats. Would have to be updated to use mgnl:asset and other new node types - Code needs some cleanup - Testing The use cases I envision are something like this: - Create a GIT repo for your exported magnolia content. - Clone the repo onto magnolia instance1 (let's call it "dev"). Switch the repo to branch "dev". - Clone the repo onto magnolia instance2 (let's call it "test"). Switch the repo to branch "test". - Export some content on instance1 into the git workspace - Commit and Push on instance1. - Export some content on instance2 into the git workspace - Commit and Push on instance2. - On a separate machine, clone the git repo, and merge branch "dev" into "test". - Pull on instance2. - Import content on instance2. In other words, using the module in combination with a git workspace, it should be possible to transport and merge JCR data between your magnolia instances. In addition all JCR data will be checked in and versioned thanks to GIT. This is the mode of working that we are trying to get to in our projects here. Regards from Vienna, Richard > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:user-list-owner@magnolia- > cms.com] Im Auftrag von Matteo Pelucco (via Magnolia Forums) > Gesendet: Freitag, 14. März 2014 14:03 > An: Magnolia User List > Betreff: [magnolia-user] Re: Develop in team > > Hi Davide, > OpenMind has a module able to automatically extract JCR nodes on > filesystem, but it is quite old. > I have in mind to develop something very easy, for developers: > > 1) you configure the paths you want to extract > 2) you configure a cron (or push a button) > 3) you configure the filesystem folder > > the app (because it will be an app) periodically extracts JCR xml files. > > you can also have observation in place.. but I think it is simpler to use a > cron. > M. > > -- > 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]> > ---------------------------------------------------------------- ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
