Product SiteDocumentation Site

13.5. Providing Customized Configuration

Like with all modules from http://puppetmanaged.org, providing customized configuration comes down to putting the right file in the right place. We'll iterate over the different locations for each managed resource.

13.5.1. /etc/httpd/conf/httpd.conf

The master configuration file for httpd is /etc/httpd/conf/httpd.conf. To customize the version that ships with the module, provide a httpd.conf in one of the following locations:
  1. puppet:///private/$environment/webserver/httpd.conf.$hostname
    A hostname specific, custom configuration file from the domain specific configuration tree. Note that this file is also environment specific. In the environment specific SCM branch for your domain specific configuration tree, this location corresponds with webserver/httpd.conf.$hostname.
  2. puppet:///private/$environment/webserver/httpd.conf
    A domain wide, custom configuration file from the domain specific configuration tree. Note that this file is also environment specific. In the environment specific SCM branch for your domain specific configuration tree, this location corresponds with webserver/httpd.conf.
  3. puppet:///files/webserver/httpd.conf.$hostname
    A site wide, custom configuration file for one host. This is no domain specific configuration file anymore, and as such is useful when you do not use domain specific configuration trees or staging environments. Also, note that this file is not environment specific. In the SCM, this location corresponds with files/webserver/httpd.conf.$hostname.
  4. puppet:///files/webserver/httpd.conf
    A site wide, custom configuration file. This is no domain specific configuration file anymore, and as such is useful when you do not use domain specific configuration trees or staging environments. Also, note that this file is not environment specific. In the SCM, this location corresponds with files/webserver/httpd.conf.
  5. puppet:///webserver/httpd.conf
    The stock httpd.conf that comes with the module. This represents or should represent the best default, for lack of a better phrasing. It should represent exactly the same as the situation right after you have performed a yum install of the httpd package.