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

Go to file

Ryan Peck 993e836f60 Fix case where state != enabled caused error When using the register_site state, if the `state` for the site in the apache pillar did not equal "enabled" the error ``` Cannot extend ID 'a2ensite <name>' in 'base:apache.register_site'. It is not part of the high state. ``` If statements were there to build out the `a2ensite` or `a2dissite` ID appropiately, but the next state for managing the config always assumed that the `a2ensite` id would be there. Addressed by making a Jinja variable that will be the appropiate ID, probably could use a better name.		2015-03-10 16:52:24 -04:00
apache	Fix case where state != enabled caused error	2015-03-10 16:52:24 -04:00
LICENSE	Add LICENSE.	2013-07-27 20:31:20 +02:00
pillar.example	Add example code for new templates 'redirect.tmpl' and 'proxy.tmpl'.	2015-02-15 00:12:13 +01:00
README.rst	Drop references to unused apt and php formulas	2015-03-02 23:38:20 +01: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.modules`

Enables and disables Apache modules.

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

Enables the Apache module mod_proxy.

apache.mod_proxy_http -------------------

Enables the Apache module mod_proxy_http and requires the Apache module mod_proxy to be enabled.

`apache.mod_wsgi`

Installs the mod_wsgi package and enables the Apache module.

apache.vhosts.standard -------------------------

Configures Apache name-based virtual hosts 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

`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'