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

OP#409 initial commit after fork

Browse Source
This commit is contained in:
12ww1160
2026-02-03 00:41:35 +01:00
parent 3fe5000d8e
commit 526aed6b88
27 changed files with 256 additions and 221 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/file.README.html
View File

@@ -60,7 +60,7 @@
<div id="content"><div id='filecontents'>
<h1 id="label-README">README</h1>
<p><a href="https://jenkins.confdroid.com/job/cd_apache/"><img src="https://jenkins.confdroid.com/buildStatus/icon?job=cd_apache"></a></p>
<p><a href="https://jenkins.confdroid.com/job/confdroid_apache/"><img src="https://jenkins.confdroid.com/buildStatus/icon?job=confdroid_apache"></a></p>
<p>[[<em>TOC</em>]]</p>
@@ -68,7 +68,7 @@
<p><code>Apache httpd</code> is a very powerful and widely used web server.</p>
<p><code>cd_apache</code> automates the installation and configuration of httpd. This module is a base module simply providing the httpd service itself to be used by other role- or profile modules, adding more detailed configurations specific to the particular use case, like for instance Wordpress.</p>
<p><code>confdroid_apache</code> automates the installation and configuration of httpd. This module is a base module simply providing the httpd service itself to be used by other role- or profile modules, adding more detailed configurations specific to the particular use case, like for instance Wordpress.</p>
<h2 id="label-WARNING">WARNING</h2>
@@ -116,7 +116,7 @@
<p>Nagios etc.</p>
</li></ul>
<p>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 <code>cd_apache</code> 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 <code>cd_apache</code> as requirement (i.e. require cd_apache) so it gets installed automatically.</p>
<p>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 <code>confdroid_apache</code> 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 <code>confdroid_apache</code> as requirement (i.e. require confdroid_apache) so it gets installed automatically.</p>
<h3 id="label-Dependencies">Dependencies</h3>
@@ -133,14 +133,14 @@
<p>via site.pp or nodes.pp</p>
<pre class="code ruby"><code class="ruby">node &#39;example.example.net&#39; {
include cd_apache
include confdroid_apache
}
</code></pre>
<ul><li>
<p>through Foreman:</p>
</li></ul>
<p>In order to apply parameters through Foreman, <strong>cd_apache::params</strong> must be added to the host or host group in question.</p>
<p>In order to apply parameters through Foreman, <strong>confdroid_apache::params</strong> must be added to the host or host group in question.</p>
<p>See <a href="https://confdroid.com/2017/05/deploying-our-puppet-modules/">more details about class deployment on Confdroid.com</a>.</p>