Product SiteDocumentation Site

13.5.5. /etc/httpd/includes.d/listen.conf

This configuration file configures what ports and IP addresses the webserver should create listener sockets. You will probably be changing this file on a per-node, per-group, per-domain or per-site basis.
  1. puppet:///private/$environment/webserver/includes.d/listen.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/includes.d/listen.conf.$hostname.
  2. puppet:///private/$environment/webserver/includes.d/listen.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/includes.d/listen.conf.
  3. puppet:///files/webserver/includes.d/listen.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/includes.d/listen.conf.$hostname.
  4. puppet:///files/webserver/includes.d/listen.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/includes.d/listen.conf.
  5. puppet:///webserver/includes.d/listen.conf
    The stock listen.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.