On Thu, Feb 25, 2010 at 7:00 PM, Sheryl <[email protected]> wrote:
>
>>> What benefit does this give you over running VirtualHost?
>>>
>>
>> (I wouldn't set up a second instance like suggested, but..)
>
> Curious about why not...
>
> BTW, my example was a little simplified. In practice we actually make a
> link "base" which points to the apache directory and the link bin to
> base/bin, etc. That way, when we compile a new version we put it in its
> own directory and change the link. Easy to upgrade, easy to back off if
> it doesn't work.
>
Because it isn't needed. If you don't need to change compile time
options, all apache needs to run is a different config file, not a
replication of the /usr/local/ hierarchy.
In fact, we use freebsd, and install apache from ports, using the
supplied rc script to manage 'profiles', which define the separate
instances of apache to run, with all necessary configuration in
/usr/local/etc/apache22-{profile-name}. No crazy symlinks required!
When a developers needs an apache instance to play with, they would
typically just do something like this:
'/usr/local/sbin/httpd -f /home/foo/proj/conf/httpd.conf'. The only
things they need in conf are the httpd.conf, mime.types and magic.
Typically, they'll declare a server root in the conf file, with a logs
folder below server root. That's pretty muc hall that is needed.
However, we don't do this so much anymore. Now typically, we will
configure a separate freebsd jail for each service.
Cheers
Tom
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
" from the digest: [email protected]
For additional commands, e-mail: [email protected]
