Best practise for Apache Virtual Hosts


As linux consultants we often work on systems that have been configured by someone else. Some of these systems have grown into webservers with a number of websites running as virtual hosts. Depending on the level of skill and insight the original system admin had, the apache configuration files can end up a tangled rats nest. I think this stems from the apache docs for vhost, albeit being very good, not give any guidelines on best practise for managing configuration files. Leading to people editing httpd.conf, to add virtual hosts, which soon gets mangled up. To make your virtual hosts manageable, the best practise is to use configuration files in /etc/httpd/conf.d/ for everything. Do not edit any of the config files in /etc/httpd/conf/ unless you really have to. A good starting point is to use a seperate file for each website. Or if you have specific needs create seperate configuration files to define difference web services. 



Block adverts and speed up internet access with a proxy server

The days of speeding up internet access using a caching proxy server are pretty much over. The idea of caching is theoritically sound, but the majority of your proxy log is generally just "TCP_MISS", dynamic content having taken over the internet. All however is not lost, using access control lists with a proxy server you can improve the speed of web browsing along with the overall experience by blocking ads. The defacto open source caching proxy is squid.

Subscribe to RSS - apache