Where are people keeping their config directories these days?

5 views
Skip to first unread message

Gary Moore

unread,
Dec 14, 2010, 3:03:18 PM12/14/10
to athena-tix-devel
ATHENA will, at least initially, be a bunch of war files deployed to Glassfish. We want configuration to still be up to the installer, though. I need opinions on an external (to the web container) configuration directory. Thew directory will likely hold our Spring configuration files, logging config files, and possible some other resources that the applications need. It will, essentially, be a shared /src/main/resources directory.

- Where should be keep this config directory? /var/athena? /usr/local/athena? c:\something?
- Should we let the user specify the location then set an ATHENA_HOME environment variable?
- What security/permission concerns surround a config directory setup like this?
- Should we encourage the use of an "athena" user who owns this directory and the files?

Gary

--
Gary Moore | gary....@fracturedatlas.org | @gsmoore
Fork us on Github: http://github.com/fracturedatlas/
Join us on IRC: ##athena on irc.freenode.net

Justin L. Karr

unread,
Dec 17, 2010, 4:24:37 PM12/17/10
to athena-t...@googlegroups.com
Gary,

I like conforming to system standards. I don't know what this would be for Windows Server, but on the UNIXen (save maybe OSX), it would be fine for us to put it under /opt, which is endorsed on every platform I've worked on (though some do prefer /usr/local). I do think we should follow an ATHENA_HOME environment variable in our configuration and run scripts to allow people to change this.

I like /opt because software there is traditionally contained as opposed to spread throughout a filesystem. You don't put your binaries in /opt/bin and your libraries in /opt/lib. You put everything in /opt/athena. I would put our configuration files in /opt/athena/config.

Most of all I do like having an ATHENA_HOME variable that lets people move it around as they see fit.

Justin

fintan donaghy

unread,
Dec 21, 2010, 4:13:14 AM12/21/10
to athena-t...@googlegroups.com

I personally like to contain everything to do with a product in one directory tree so that a full uninstall is done by rm -rf <product root>

--
Visit: http://athena.fracturedatlas.org/tix
Fork: http://github.com/fracturedatlas
Chat: ##athena on Freenode
 
You received this email because you are subscribed to the "ATHENA Tix Developers" group on Google Groups.
 
To post, email: athena-t...@googlegroups.com
To unsubscribe, email: athena-tix-dev...@googlegroups.com
For more, visit: http://groups.google.com/group/athena-tix-devel?hl=en

Reply all
Reply to author
Forward
0 new messages