I am looking for some advice on managing multiple development instances using 
the Magnolia Community Edition. Ideally I would like to be able to work on 
multiple features at the same time that are (somewhat) independent from each 
other. Our setup is as follows:

- Instance of Tomcat with author/ROOT.
- We have docroot/templates managed under version control.
- We have our own module in WEB-INF/lib managed under version control.
- Anything magnolia related (templates, dialogs, paragraphs, config) is managed 
by hand and move from one instance to another using magnolia export/import.
- From time to time we copy production and put it on our development instances 
to keep things up-to-date.
- All development instances sit on a server on our network accessible to 
developers.


Right now we have two development instances that are completely independent 
from each other i.e their own tomcat, docroot/templates/module, and magnolia 
repo. This turns into a hassle because more often than not one instance gets 
way out of date from the other, making the older instance useless until someone 
(me) synchronizes it. I can see firing up a third maybe a fourth instance in 
the future as we work on new things or have R&D todo. I'm starting to think 
that maybe all these instances should share the same persistence manager. 
Should I move the repository to a common place? Should I move to PostgresSQL? 
If you recommend I do something like that, what things will I need to change to 
make this work? Is there any other advice someone can provide that will help? 
It would be greatly appreciated!

Using Magnolia 4.4.8 right now but will be moving to 5.x in the near future.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=982f6ba9-978f-488c-8dc0-a5fa9c06fb23


----------------------------------------------------------------
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]>
----------------------------------------------------------------

Reply via email to