Set up and configure the Apache HTTP server https://github.com/saltstack-formulas/apache-formula

Go to file

Raphaël Hertzog 4fa9d57d2b Do not force usage of apache.config in apache.vhosts.standard In `4d04d95b02` (#113) apache/vhosts/standard.sls has been modified by @genuss to include apache.config on the basis that apache.config was now able to retrieve the interfaces/ports from pillar data in apache:sites. I use apache:sites to register virtual hosts with non-standard "template_file" (they contain the desired configuration directly) and the "interface/port" keys are thus not meaningful. apache: sites: example.com: template_file: salt://vm/example/apache-vhost.conf DocumentRoot: False The generated ports.conf ends up containing only "*:80" while my virtual host configuration files need ports 80 and 443. The situation was perfectly fine up to now because the default configuration file handles both of those ports if you have mod_ssl installed. People who want to use apache.config should just explicitly include that state, we should not force its usage to all apache.vhosts.standard users.		2016-06-21 17:39:35 +02:00
.github	Pull Request Template	2016-04-11 09:59:39 -05:00
apache	Do not force usage of apache.config in apache.vhosts.standard	2016-06-21 17:39:35 +02:00
test	Add mod_security management	2016-05-11 15:41:07 -03:00
.gitignore	Add mod_security management	2016-05-11 15:41:07 -03:00
.kitchen.yml	Add mod_security management	2016-05-11 15:41:07 -03:00
FORMULA	Initial commit of SPM FORMULA	2015-07-07 09:45:40 -06:00
LICENSE	Update LICENSING year	2015-03-20 20:10:44 -04:00
pillar.example	Add proxyrequests directive (#144 )	2016-05-24 10:10:01 -07:00
README.rst	enable mod_ssl on Redhat	2016-05-18 10:07:24 +02:00

README.rst

apache

Formulas to set up and configure the Apache HTTP server.

Note

See the full Salt Formulas installation and usage instructions.

Available states

`apache`

Installs the Apache package and starts the service.

`apache.config`

Configures apache based on os_family

`apache.mod_mpm`

Configures the apache mpm modules on Debian mpm_prefork, mpm_worker or mpm_event (Debian Only)

`apache.modules`

Enables and disables Apache modules.

`apache.mod_rewrite`

Enabled the Apache module mod_rewrite (Debian only)

apache.mod_proxy -------------------

Enables the Apache module mod_proxy. (Debian only)

`apache.mod_proxy_http`

Enables the Apache module mod_proxy_http and requires the Apache module mod_proxy to be enabled. (Debian Only)

`apache.mod_wsgi`

Installs the mod_wsgi package and enables the Apache module.

`apache.mod_actions`

Enables the Apache module mod_actions. (Debian Only)

`apache.mod_headers`

Enables the Apache module mod_headers. (Debian Only)

`apache.mod_pagespeed`

Installs and Enables the mod_pagespeed module. (Debian and RedHat Only)

`apache.mod_php5`

Installs and enables the mod_php5 module

`apache.mod_fcgid`

Installs and enables the mod_fcgid module

apache.mod_dav_svn --------------------

Installs and enables the mod_dav_svn module (Debian only)

apache.mod_security ----------------------

Installs an enables the Apache mod_security2 WAF<http://modsecurity.org/>`_ using data from Pillar. (Debian and RedHat Only)

Allows you to install the basic Core Rules (CRS) and some basic configuration for mod_security2

`apache.mod_ssl`

Installs and enables the mod_ssl module (Debian and RedHad only)

apache.mod_vhost_alias ----------------------

Enables the Apache module vhost_alias (Debian Only)

apache.mod_remoteip ----------------------

Enables and configures the Apache module mod_remoteip using data from Pillar. (Debian Only)

apache.own_default_vhost --------------------------

Replace default vhost with own version. By default, it's 503 code. (Debian Only)

apache.no_default_vhost --------------------------

Remove the default vhost. (Debian Only)

`apache.vhosts.standard`

Configures Apache name-based virtual hosts and creates virtual host directories using data from Pillar.

Example Pillar:

apache:
  sites:
    example.com: # must be unique; used as an ID declaration in Salt; also passed to the template context as {{ id }}
      template_file: salt://apache/vhosts/standard.tmpl

When using the provided templates, one can use a space separated list of interfaces to bind to. For example, to bind both IPv4 and IPv6:

apache:
  sites:
    example.com:
      interface: '1.2.3.4 [2001:abc:def:100::3]'

`apache.manage_security`

Configures Apache's security.conf options by reassinging them using data from Pillar.

`apache.debian_full`

Installs and configures Apache on Debian and Ubuntu systems.

These states are ordered using the order declaration. Different stages are divided into the following number ranges:

apache will use 1-500 for ordering
apache will reserve 1 -100 as unused
apache will reserve 101-150 for pre pkg install
apache will reserve 151-200 for pkg install
apache will reserve 201-250 for pkg configure
apache will reserve 251-300 for downloads, git stuff, load data
apache will reserve 301-400 for unknown purposes
apache will reserve 401-450 for service restart-reloads
apache WILL reserve 451-460 for service.running
apache will reserve 461-500 for cmd requiring operational services

Example Pillar:

apache:
  register-site:
    # any name as an array index, and you can duplicate this section
    {{UNIQUE}}:
      name: 'my name'
      path: 'salt://path/to/sites-available/conf/file'
      state: 'enabled'