updated README with vhost details and updated version
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
|Repo Name| version | Build Status|
|
||||
|---|---|---|---|
|
||||
|`cd_apache`| 0.0.1.0 | [](https://jenkins.confdroid.com/job/cd_apache/)|
|
||||
|`cd_apache`| 0.0.1.1 | [](https://jenkins.confdroid.com/job/cd_apache/)|
|
||||
|
||||
### Synopsis
|
||||
`Apache httpd` is a very powerful and widely used web server.
|
||||
@@ -52,7 +52,7 @@ As stated in the ynopsis, this module was written particularly for usage as base
|
||||
* WordPress
|
||||
* 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. The exact layout for your particular vhost configuration files depend a lot on your application and organization requirements, and cannot be predicted from outside per se.
|
||||
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.
|
||||
|
||||
### Repo Structure
|
||||
Repostructure as been moved to REPOSTRUCTURE.md
|
||||
|
||||
Reference in New Issue
Block a user