On Tue, 4 Sep 2007 18:05:32 -0500 "Aaron Griffin" <[EMAIL PROTECTED]> wrote: > Well we should also _create_ those directories then... I mean, what > does apache do if the document root doesn't exist? I expect it to fail > to start, which we don't want by default. Or the package could create it, not filesystem.
On Tue, 4 Sep 2007 18:05:32 -0500 "Aaron Griffin" <[EMAIL PROTECTED]> wrote: > So the real question is - do we create 3-4 different empty document > roots, or always use the same one? Back to the "don't put web packages in the package manager". Anyone that has two web servers installed knows what they are doing, and probably serves different content off the different servers. So we should give each server a document root. As for web packages, there is no possible way of knowing where it should intall or if the person even uses the default roots. It comes back to the fact that we shouldn't have web packages. > On 9/4/07, Martin Brandenburg <[EMAIL PROTECTED]> wrote: > > Using /srv for all server root dirs does sound like a good idea, but it > > would be more simple (and KISS) to just leave root dirs as the source > > package defaults as long as they don't conflict. > > Well we should also _create_ those directories then... I mean, what > does apache do if the document root doesn't exist? I expect it to fail > to start, which we don't want by default. > > So the real question is - do we create 3-4 different empty document > roots, or always use the same one? > > _______________________________________________ > arch mailing list > [email protected] > http://archlinux.org/mailman/listinfo/arch -- Martin Brandenburg <[EMAIL PROTECTED]> _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
