[ale] Mapping VirtualHosts to public_html

[James Sumners]

I believe that will redirect all requests on port 80 to the specified
public_html. So if you are hosting example.com and elpmaxe.com on that
box then requests to both domains will go to that public_html. Other
than that, to the best of my recollection, that will work.

On Jan 7, 2008 3:42 PM, Christopher Fowler <cfowler at outpostsentinel.com> wrote:
> I've configured public_html support in Apache and I want to move our
> website down to a server at Qualty.  I would like to place everything
> in /home/outpostsentinel/public_html  and create a VirtualHost for that.
>
> Is this the correct way?
>
> #
> # Use name-based virtual hosting.
> #
> NameVirtualHost *:80
> #
> # NOTE: NameVirtualHost cannot be used without a port specifier
> # (e.g. :80) if mod_ssl is being used, due to the nature of the
> # SSL protocol.
> #
>
> #
> # VirtualHost example:
> # Almost any Apache directive may go into a VirtualHost container.
> # The first VirtualHost section is used for requests without a known
> # server name.
> #
> <VirtualHost *:80>
>     DocumentRoot /home/outpostsentinel/public_html
>     ServerName www.outpostsentinel.com
> </VirtualHost>
>
> I've given the public_html directories proper permissions.  will apache
> see this and do the right thing?  I think he runs and external program
> and changes permissions to the user for the sake of running CGIs as the
> user.



-- 
James Sumners
http://james.roomfullofmirrors.com/

"All governments suffer a recurring problem: Power attracts
pathological personalities. It is not that power corrupts but that it
is magnetic to the corruptible. Such people have a tendency to become
drunk on violence, a condition to which they are quickly addicted."

Missionaria Protectiva, Text QIV (decto)
CH:D 59