confdroid/confdroid_apache
3
0
Fork 0
Code Issues Projects Wiki Activity

EN-0001 - spellcheck

Browse Source
This commit is contained in:
Arne Teuke
2021-08-05 16:33:51 +02:00
parent 27c4ce3f4e
commit 9902499773
2 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
.spelling
View File

@@ -20,3 +20,6 @@ ConfDroid
nagios nagios
vHosts vHosts
vHost vHost
phpMyAdmin
phpPgAdmin
parameterized

8
README.md
View File

@@ -36,14 +36,14 @@ Maintenance
### vHosts ### vHosts
As stated in the synopsis, this module was written particularly for usage as base module. `Apache httpd` has a great number of use cases where it actually is not used directly as full blown webserver by itself, but instead as platform for other applications. Examples here would be: As stated in the synopsis, this module was written particularly for usage as base module. `Apache httpd` has a great number of use cases where it actually is not used directly as full-blown web server by itself, but instead as platform for other applications. Examples here would be:
* frontend proxy for other applications to avoid having to put the port number into the URL * front-end proxy for other applications to avoid having to put the port number into the URL
* applications like phpMyAdmin, phpPgAdmin * applications like phpMyAdmin, phpPgAdmin
* WordPress * WordPress
* Nagios etc. * Nagios etc.
With those use cases, you would provide the vHosts at the Puppet module for the application, not the base module. Also, if you plan to use this module to run a plain fully fledged web server, you would use a role- or profile class/module on top of `cd_apache` to set up your vHost exactly as needed. Examples for regular basic vHost configuration files are included in the examples directory as parameterized .erb files. You would create a define for vhosts, i.e. using the example parameters, and simply add `cd_apache` as requirement (i.e. require cd_apache) so it gets installed automatically. With those use cases, you would provide the vHosts at the Puppet module for the application, not the base module. Also, if you plan to use this module to run a plain fully fledged web server, you would use a role- or profile class/module on top of `cd_apache` to set up your vHost exactly as needed. Examples for regular basic vHost configuration files are included in the examples directory as parameterized .erb files. You would create a define for vHosts, i.e. using the example parameters, and simply add `cd_apache` as requirement (i.e. require cd_apache) so it gets installed automatically.
### Dependencies ### Dependencies
@@ -65,7 +65,7 @@ node 'example.example.net' {
* through Foreman: * through Foreman:
In order to apply parameters through Foreman, **__cd_apache::params__** must be added to the host or hostgroup in question. In order to apply parameters through Foreman, **__cd_apache::params__** must be added to the host or host group in question.
See [more details about class deployment on Confdroid.com](https://confdroid.com/2017/05/deploying-our-puppet-modules/). See [more details about class deployment on Confdroid.com](https://confdroid.com/2017/05/deploying-our-puppet-modules/).