Re: /usr/local/www a tradition?
like system update? keep it clean keep it simple what will happen if you will decide to update system/software and everything will be in random places not where is should be? I'm not too concerned with that. Automatic system updates are the key to temporal instability, arguably at the cost of security, but that's another story best saved for later... I dislike the notion of putting project-specific data under /usr/local. Config files and the like are easy to control, but large trees should be able to live wherever I want them to live. I concur. I thought it would be easiest to keep all non-system data in one place (/home), but thought I'd best get the general consensus first. You have all been quite helpful. Thank you much. -Modulok- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/local/www a tradition?
On Thu, Mar 13, 2008 at 07:29:55PM -0600, Modulok wrote: Is there a compelling reason for placing subversion and web-server data in /usr/local and not somewhere else? I was thinking of keeping all user accounts (human and daemon alike) in one place like, /home/www and /home/svn and so forth. Before I break convention, I just thought I'd see if placing said files in /usr/local was just a tradition or if there was another reason for it. You probably won't break anything, but it is the convention for FreeBSD structure. see: man hier Some things are easier to install when following the conventions because you have to do less special-casing and modifying config files. There may be some badly written utility out there that does not properly check config files and just assumes things are in the conventional places.I don't know of any and FreeBSD tries to avoid this problem. But, the time you find out is usually the most inconvenient time. So, you pays your money and you takes your chances. jerry Thanks. -Modulok- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/local/www a tradition?
On Thu, Mar 13, 2008 at 07:29:55PM -0600, Modulok wrote: Is there a compelling reason for placing subversion and web-server data in /usr/local and not somewhere else? I was thinking of keeping all user accounts (human and daemon alike) in one place like, /home/www and /home/svn and so forth. Before I break convention, I just thought I'd see if placing said files in /usr/local was just a tradition or if there was another reason for it. Break the convention! Where apache or any other web server looks for its home is down to *your* apache config. Different vhosts can look wherever they like for their own homes and you can put them wherever you like - no need for them to be in the same place at all. So one vhost could look in /home/project1 and another in /home/project2/Web, for example. You could keep the default server in /usr/local/www and then you get the files the port installs by default, but still control where *your* data goes. I don't know how tied subversion is to it's home in /usr/local but I would hope not at all. /home/cvs has been the home of my CVS repositories for a long time and if I switched VCS I'd certainly want to follow a pattern like that (certainly for anything that follows a CVS-like model, which subversion does. Something like Hg might be another matter, but then I'd be looking at putting repositories in project-specific locations). I dislike the notion of putting project-specific data under /usr/local. Config files and the like are easy to control, but large trees should be able to live wherever I want them to live. One can usually work around any issue that arise, and if you hit trouble, just mail back here :-) --Alex PS You said demons and I'd certainly draw a line between a demon like, say, postfix or bind which has a system-role and ones like apache, subversion or a database which have a project-role. Not sure it's a very firm line though - plenty of grey area. For me, if it's manageable with a simple CVSed config file or ten, then it can stay in /usr/local. If it breeds data, then it belongs somewhere else. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/local/www a tradition?
On Friday 14 March 2008 16:48:18 Alex Zbyslaw wrote: On Thu, Mar 13, 2008 at 07:29:55PM -0600, Modulok wrote: Is there a compelling reason for placing subversion and web-server data in /usr/local and not somewhere else? I was thinking of keeping all user accounts (human and daemon alike) in one place like, /home/www and /home/svn and so forth. Before I break convention, I just thought I'd see if placing said files in /usr/local was just a tradition or if there was another reason for it. Break the convention! Where apache or any other web server looks for its home is down to *your* apache config. Different vhosts can look wherever they like for their own homes and you can put them wherever you like - no need for them to be in the same place at all. Depends a bit on the user's defenition of 'data'. For some, 'data' includes apps like phpMyAdmin, for some it doesn't. Anything installed by ports should remain in /usr/local. Self-respecting webservers support aliasing weblocations to physical directories, so in most cases it can be worked around. In the event you need multiple installations of the same webapp, either use jails or don't use the ports to install them (and then also don't put them in /usr/local). -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/usr/local/www a tradition?
Is there a compelling reason for placing subversion and web-server data in /usr/local and not somewhere else? I was thinking of keeping all user accounts (human and daemon alike) in one place like, /home/www and /home/svn and so forth. Before I break convention, I just thought I'd see if placing said files in /usr/local was just a tradition or if there was another reason for it. Thanks. -Modulok- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/local/www a tradition?
On Thursday 13 March 2008, Modulok said: Is there a compelling reason for placing subversion and web-server data in /usr/local and not somewhere else? I was thinking of keeping all user accounts (human and daemon alike) in one place like, /home/www and /home/svn and so forth. Before I break convention, I just thought I'd see if placing said files in /usr/local was just a tradition or if there was another reason for it. Thanks. -Modulok- Actually you can put webdata anywhere you want. It's common for virtual host sites to be in ~/htdocs so the user has write access to their site. Beech -- --- Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
