In the apache configs on our web servers what is the difference between the entries in the sites-enabled directory and the sites-available directory? More importantly, which should be the basis for the list of sites I need to put into Nagios? If I had to guess I'd go with sites-enabled, but I'd rather not guess. -- Adam
sites-enabled are just symlinks to files in sites-available. When you make a site live with apache2, you symlink the config into sites-enabled. The webserver then reads that directory on startup. Yes, we should only be monitoring what's in sites-enabled. Ken On 06/15/2011 12:48 PM, Adam Duston wrote:
In the apache configs on our web servers what is the difference between the entries in the sites-enabled directory and the sites-available directory? More importantly, which should be the basis for the list of sites I need to put into Nagios? If I had to guess I'd go with sites-enabled, but I'd rather not guess.
-- Adam
These directories are used specifically in Debian/Ubuntu Apache configurations. sites-available stores all the site specific configuration files, similar to conf.d in red hat/centos. I'd put your nagios config here. sites-enabled stores symlinks to configurations in sites-available. You can either manage these symlinks manually, or with the a2ensite / a2dissite commands. Jason On Jun 15, 2011, at 12:48 PM, Adam Duston wrote:
In the apache configs on our web servers what is the difference between the entries in the sites-enabled directory and the sites-available directory? More importantly, which should be the basis for the list of sites I need to put into Nagios? If I had to guess I'd go with sites-enabled, but I'd rather not guess.
-- Adam
participants (3)
-
Adam Duston -
Jason Hedden -
Ken Raffenetti