Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Sep 2007 07:15:21 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Eric <eric@mikestammer.com>
Cc:        Robert Huff <roberthuff@rcn.com>, questions@freebsd.org, rafan@freebsd.org
Subject:   Re: apache22 web root directive
Message-ID:  <46E4E0F9.5020207@infracaninophile.co.uk>
In-Reply-To: <46E4A0E0.1010709@mikestammer.com>
References:  <46E482D7.8000305@mikestammer.com>	<18148.38048.334086.419648@jerusalem.litteratus.org> <46E4A0E0.1010709@mikestammer.com>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Eric wrote:

> close, but I am not running in a non standard DocumentRoot as far as I
> know. its set to apache22's /usr/local/www/apache22/data, which is the
> default, but if you look at the mailgraph Makefile, it uses
> /usr/local/www/data for the install.
> 
> the more i look at it, the more it seems like its a mailgraph issue.
> 
> i guess I am curious of the apache20 default of /usr/local/www/data was
> around so long its just what everyone assumes, but from what I can tell,
> thats not the recommended practice. isnt it better to install to
> /usr/local/www/mailgraph and then alias things?

Web-based applications will generally install into a subdirectory of
/usr/local/www independent of what web server you use.  There are
some exceptions -- eg. cacti installs into /usr/local/share/cacti

This means that you will have to make provision in your httpd.conf
(or whatever the equivalent is for the webserver you're using) so
that the filesystem space the application lives in is mapped into
the URL-space provided by your webserver.  In apache, that typically
means setting up an alias and then applying appropriate access
controls in a <Location> or <Directory> block.

Formerly many web applications installed into the apache specific
directory /usr/local/www/data but this behaviour is now discouraged.
It's not, AFAIK, absolutely forbidden, but you'ld have a hard time
getting a new port through committal if it behaved like that. I
don't think there has been a concerted effort to find all of the
older ports that install under /usr/local/www/data and modify them;
rather individual maintainers are expected to modify their ports as
the occasion arises.

	Cheers,

	Matthew

- --
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                  Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG5OD58Mjk52CukIwRCBpLAJ9Uic70kt6wry0Fn6liuGE21ckkowCfb1qH
PHKdfmrcqyH1YVrC3hnOdJM=
=rbh6
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46E4E0F9.5020207>