Hi Joe, I think that several approaches are possible. It strongly depends on your scenario:
1) You work on your local instance and you have finish your work --> pass your collegue the repository. He can have a fresh Magnolia instance with all your modification already there 2) You want to work togheter --> Use one installation as a master: every configuration must be done on that instance, then passed to the other. 2 ways: A) direct activation (just add the other instance as a subscriber) B) export/import JCR xml 3) You are working with a PROD environment (e.g.: your site has already been deployed once): --> You can use version handler and SVN/GIT. You can track your changes into SetPropertyTasks, ChangePropertyTask, BootstrapTasks... (see core module for more info). Merging is more easy with a SCM than in plain XML files. Just work with small chunk of XML and actions. You can trigger a version handling simply changing the version of a module back (e.g.: 5.1.1 --> 5.1.0 will trigger at next reboot the version handling for version 5.1.1). About other question: YES: you can have a public instance that activate on author instance (not a best practice). But just remember that author and public have different settings. Pay attention. HTH! Matteo -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=20ca2cd8-a609-4dd9-a913-1441e3bfdcbb ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
