Installing ApacheIn the second part to a six-part series on Apache installation and configuration, we will focus on selecting modules to install and begin to explore configuration and hardening. This article is excerpted from chapter two of Apache Security, written by Ivan Ristic (O'Reilly; ISBN: 0596007248). Copyright © 2006 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.
print this article SEARCH DEV SHED |
In this chapter, I will assume the following locations for the specified types of files: Binaries and supporting files Public files Private web server or application data Publicly accessible CGI scripts Private binaries executed by the web server Log files Installation locations are a matter of taste. You can adopt any layout you like as long as you use it consistently. Special care must be taken when deciding where to store the log files since they can grow over time. Make sure they reside on a partition with enough space and where they won’t jeopardize the system by filling up the root partition. Different circumstances dictate different directory layouts. The layout used here is suitable when only one web site is running on the web server. In most cases, you will have many sites per server, in which case you should create a separate set of directories for each. For example, you might create the following directories for one of those sites: /var/www/apachesecurity.net/bin A similar directory structure would exist for another one of the sites: /var/www/modsecurity.org/bin
blog comments powered by Disqus |
Getting Started with Apache
