I have just seen the /var/
directory being defined as:
Multi-purpose log, temporary, transient, and spool files. A memory-based file system is sometimes mounted at /var.
Whereas /usr/
has been described as:
The majority of user utilities and applications.
and /usr/share/
is:
Architecture-independent files.
To my eye, it looks like web apps I write fall under "user utilities and applications" (but this is a server, so storing this stuff under my home directory is impractical if I want other admins to work on it). My web apps have nothing to do with the 'system architecture'.
Hence, /usr/share/www/
looks like a great place to store web apps and serve from, as opposed to /var/www/
. I am aware apache server's convention is to store in /var/
, but I'm using a different server and even if I was using apache, I don't mind stepping on this particular convention's toes.
My question is, any compelling arguments against using this directory?
hier(7)
. FWITW, on my server I use a separate partition mounted on/www/
instead of/var/www/
./usr/local/
seems to have many conventions already set up for this purpose./www/
(separately mounted if possible) seems like the very best option.../opt/
is a good candidate, and the description on Wikipedia for this directory sounds great as well! Ah... so many choices :)