So, we have 2 directories that need to be created for every instance - /deploy /varThe easiest way to keep users (who will have less working knowledge of Geronimo than us developers) from screwing up their server when trying to use multiple instances, is to put both of those directories under another "instance" directory, including the base template files.
Can't we just reorganize the existing layout to be a simpler - GHOME/<instances>/template/var/... GHOME/<instances>/template/deploy/ GHOME/<instances>/default/var/... GHOME/<instances>/default/deploy/ where <instances> could be a word we all vote on, like "instances" or "servers".That way, we always have a "default" server configured and available for users and the geronimo-maven-plugin to use...
Do we need to include the /bin directory in there too, given the geronimo script has JVM options in it and may need to be customized for different instances???
I could also go along with leaving out the <instances> directory, as long as we agreed on placing the "template" files and the "default" instance in well named directories under GHOME....
-Donald Anita Kulshreshtha wrote:
--- Matt Hogstrom <[EMAIL PROTECTED]> wrote:I have to go back and see the directory layout your proposing. Iiki.apache.org/GMOxDOC20/running-multiple-instances-of-geronimo.htmldidn't see a specific proposal in the JIRASome information is here: http://cwiki.apache.org/GMOxDOC20/running-multiple-instances-of-geronimo.htmlHow about for purposes of this discussion: $G == GERONIMO_HOME We organize servers by default as:> $G/var/servers/geronimo01/configlogs tmp and have $G/var/config logs tmpbe a template that can be copied into new servers. This way users could easily customize their default.Some Background info: Currently the following dir/files are used to run an instance: deployvar - activemqcatalina config derby log security shared temp txlog I like hot deploy directory being outside of the 'var'. All these directories go under G/foo for an instance named foo. The 'var' created by build has:var configlog security tempIf the tree doesn't exist we fail with a message like: "Server instance 'geronimo03' has not been initialized. Please run the serverInstance.sh script to create a new instance."The issue here is do we make a copy (for running default instance) during build or ask our _developers_ to get used to this message and using serverInstance.sh. IIUC, you are saying that create the template and the default instance during build. And provide a script for creating additional instances.Sounds like we're almost there.yup.. Thanks Anita __________________________________________________ Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
smime.p7s
Description: S/MIME Cryptographic Signature
