Hello guys, many thanks for your ideas-sharing, very interesting approaches.
Nils: I like to use groovy as well; the only thing I have to argue here, is that an app is more comfortable for "young" developers. But the app could be a simple "push-button-and-launch-groovy" wrapper for your scripts. I'm in target with your approach :-) Richard: very, very, very interesting approach. I'm quite curious to see an example of your exported files. Basically, is a schema similar of what sometimes we did in 4.x, using the Packager. We pack instance1 files and move them to instance2.. of course, no Git, no comparison, no merge.. I am available to help you on this, if you want.. my skype is tinext_matteo_pelucco, feel free to contact me.. And more: moving (or better: merging) content from environment A (stage) to environment B (prod) and viceversa is a feature I expect, in 2014, from an Enterprise CMS. Elsadek: I've got your point, but sometimes is not affordable to have a stage machine for every project. But yes, in a ideal work, a central staging unit is a good friend. -- 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]> ----------------------------------------------------------------
