Best practice for apache on ubuntu

[Fernando Duran]

Hello,

I take "best practice" as what most people with experience do.

For Debian/Ubuntu and Apache2 this is what I do and see most:

Global server configurarion goes into apache2.conf and httpd.conf is empty. This is what comes with the package install too.

Virtual servers (site-specific settings like DocumentRoot) go into sites_available directory, using the domain name as basis for the name of the file. Under sites_enabled directories are links to sites_available. Special configurations under conf.d directory (like security). And that's pretty much it. Some people like to put the SSL version of the virtual host on the same file, other people like to put it in a separate file. 

 
---------------------
Fernando Duran
http://www.fduran.com


----- Original Message -----
> From: William Muriithi <william.muriithi-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org>
> To: TLUG mailing list <tlug-lxSQFCZeNF4 at public.gmane.org>
> Cc: 
> Sent: Thursday, September 8, 2011 1:15:39 PM
> Subject: [TLUG]: Best practice for apache on ubuntu
> 
> Hello
> 
> I came across this article and the following sentence seem not to be
> helpful in what its trying to deliver. Google is not helping with a
> better article I keep getting the same explanation.
> 
> Quote:
> httpd.conf: historically the main Apache2 configuration file, named
> after the httpd daemon. The file can be used for user specific
> configuration options that globally effect Apache2.
> End quote:
> 
> https://help.ubuntu.com/10.04/serverguide/C/httpd.html
> 
> I am curious as to what should be the content of this file as its used
> in Ubuntu.  If it was on Centos, this would be the main configuration
> file.  On Ubuntu and I assume Debian, its empty.  What is its intended
> use?  For example, if I want to change the default MPM settings,
> should it be done on apache2.conf or httpd.conf?  Its a user specific
> setting in my opinion.  In short, I get a feeling apache2.conf should
> never be edited and all changes should be on httpd.conf, including
> change to root directory.  Is this correct?
> 
> Also, what is the best practice for ssl configuration?  Should they go
> into vhost file, apache2.conf or httpd.conf?  I tend to put them on
> vhost file, but there is a lot of redundancy with this setup and it
> tend to feel a tad inefficient.
> 
> Thanks in advance
> 
> Regards,
> 
> William
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists