Setting up apache web server behind a router

[Derek Broughton]

Amedee Van Gasse (Ubuntu) wrote:

> On Tue, June 9, 2009 14:42, Derek Broughton wrote:
>> Amedee Van Gasse (Ubuntu) wrote:
>>
>>
>>>> No, that is not true.
>>>> The config files in sites-enabled are (or should be) symbolic links to
>>>>  config files in sites-available. Changes in sites-enabled are
>>>> automatically also in sites-available, because the real file is
>>>> there.
>>>>
>>>> If the files in sites-enabled are regular files, not symlinks, then
>>>> the Apache configuration is not as it should be, according to
>>>> Debian/Ubuntu
>>>> best practices.
>>
>> I don't think that follows.  Debian/Ubuntu distribute packages with files
>> in .../sites-available and symlinks in .../sites-enabled (not just
>> Apache's
>> defaults - other webapp packages may add files to those directories).
>> However, when I _personally_ create virtual hosts, I put them in
>> .../sites-
>> enabled.  I can think of no good reason - including "policy" - to go to
>> the trouble of creating an additional symlink, except to make it easy to
>> remove a virtual host without deleting the file (but you still have to
>> delete the symlink, so nothing is really gained). --
> 
> Are you familiar with a2ensite/a2dissite, and similar for modules
> a2enmod/a2dismod?
> I use those commands all the time.

I know the exist :-)

I don't use them, because I don't generally need them.  If you're 
distributing packages, then yes, it's important to follow policy.  If you're 
maintaining your own site, it's probably overkill.
-- 
derek