Christian Spoo wrote:
In my opinion, copying application's files to a webroot is something,
which I could do myself. Instead of constructing a long commandline for
webapp-config some little 'cp' commands could do the same. Hardlinking
the files saves space, but then I can't modify the sources without
affecting other installations of the same version.
Instead of the default /var directory I always created a /www dir, in
which all my sites live. That way I can have a dedicated partition for
my sites and limit /var to about 5-10GB at the same time. It's a great
pity that the mysql ebuild also installs it's datadir into the /var
tree. Perhaps something like /usr/mysql would be better for this. But
this would need a general discussion about the use of /var.
Christian
While I'm shaking off my revulsion of having a DB data dir in /usr, I
must remind my self that location doesn't matter. Symlinks give you all
of the flexibility that you need. If you want mysql's data dir to be on
the /usr partition just symlink /var/lib/mysql to /usr/mysql. Just the
same with your /www dir. You can symlink /var/www to /www and you are
good to go.
This is a great way to manage application data on extra disks or nfs
mounts, because it makes it simple to change where the data is stored
without having to modify the configuration of the application.
Joby Walker
--
[email protected] mailing list
