On Mar 4, 2008, at 10:07 AM, Scott Anders wrote:
Thanks for the feedback guys.
I think you're missing my question though. I have changed the
magnolia.repositories.home to point to a place outside of my expanded
WAR because I want the content and such to persist after I reload my
app.
In all fairness, you really should have stated that up front :P
If you are going through all the trouble of changing these configs, I
would recommend also going through the trouble of changing the
persistence manager. If you use a mySQL persistence manager
(instructions on the wiki) the repo is stored outside of the webapp
and will persist when you reload the app.
It's located at /opt/repositories. Within my WAR I have
WEB-INF/config/PhysicalMachineName/magnolia.properties. When the app
starts up it sees that file and uses the repository home at
/opt/repositories. But since I want to have two instances on the same
physical they both want to use that same repository home. How do I
tell one app to use /opt/repositories and another to use
/opt/repositoriesTest?
If you want to use one war file to run both the dev and the test, you
will need to change the names before they deploy.
change physicalMachineName to the webapp name. make a new dir for
each webapp you are going to deploy and make new dirs:
WEB-INF/config/magnoliaDev/magnolia.properties
WEB-INF/config/magnoliaTest/magnolia.properties
then rename the file to match that. I'm surprised that it worked with
the physical machine name as the parent directory for the configs,
I've always just seen it used as the webapp name.
Ryan
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
