Deployed 82dd9f6 with MkDocs version: 1.5.3

index.html

@@ -349,7 +349,8 @@
 <h1 id="rabe-nut-image">RaBe NUT Image</h1>
 <p><a href="https://networkupstools.org/">Network UPS Tools</a> container image based on <a href="https://github.com/radiorabe/container-image-ubi9-minimal">RaBe UBI9 Minimal</a>.</p>
 <h2 id="usage">Usage</h2>
-<p>Run it as you please. Not that this image does not generate any automated configuration.</p>
+<p>Run it as you please.</p>
+<p>Note that this image does not generate any automated configuration. You can inject config by putting it into the <code>/var/tmp/nut-config/</code> directory which gets copied to <code>/etc/nut</code> during startup.</p>
 <h2 id="release-management">Release Management</h2>
 <p>The CI/CD setup uses semantic commit messages following the <a href="https://www.conventionalcommits.org/en/v1.0.0/">conventional commits standard</a>.
 The workflow is based on the <a href="https://radiorabe.github.io/actions/">RaBe shared actions</a>

search/search_index.json

@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"RaBe NUT Image","text":"<p>Network UPS Tools container image based on RaBe UBI9 Minimal.</p>"},{"location":"#usage","title":"Usage","text":"<p>Run it as you please. Not that this image does not generate any automated configuration.</p>"},{"location":"#release-management","title":"Release Management","text":"<p>The CI/CD setup uses semantic commit messages following the conventional commits standard. The workflow is based on the RaBe shared actions and uses go-semantic-commit to create new releases.</p> <p>The commit message should be structured as follows:</p> <pre><code>&lt;type&gt;[optional scope]: &lt;description&gt;\n\n[optional body]\n\n[optional footer(s)]\n</code></pre> <p>The commit contains the following structural elements, to communicate intent to the consumers of your library:</p> <ol> <li>fix: a commit of the type <code>fix</code> patches gets released with a PATCH version bump</li> <li>feat: a commit of the type <code>feat</code> gets released as a MINOR version bump</li> <li>BREAKING CHANGE: a commit that has a footer <code>BREAKING CHANGE:</code> gets released as a MAJOR version bump</li> <li>types other than <code>fix:</code> and <code>feat:</code> are allowed and don't trigger a release</li> </ol> <p>If a commit does not contain a conventional commit style message you can fix it during the squash and merge operation on the PR.</p>"},{"location":"#build-process","title":"Build Process","text":"<p>The CI/CD setup uses Docker build-push Action  to publish container images. The workflow is based on the RaBe shared actions.</p>"}]}
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"RaBe NUT Image","text":"<p>Network UPS Tools container image based on RaBe UBI9 Minimal.</p>"},{"location":"#usage","title":"Usage","text":"<p>Run it as you please.</p> <p>Note that this image does not generate any automated configuration. You can inject config by putting it into the <code>/var/tmp/nut-config/</code> directory which gets copied to <code>/etc/nut</code> during startup.</p>"},{"location":"#release-management","title":"Release Management","text":"<p>The CI/CD setup uses semantic commit messages following the conventional commits standard. The workflow is based on the RaBe shared actions and uses go-semantic-commit to create new releases.</p> <p>The commit message should be structured as follows:</p> <pre><code>&lt;type&gt;[optional scope]: &lt;description&gt;\n\n[optional body]\n\n[optional footer(s)]\n</code></pre> <p>The commit contains the following structural elements, to communicate intent to the consumers of your library:</p> <ol> <li>fix: a commit of the type <code>fix</code> patches gets released with a PATCH version bump</li> <li>feat: a commit of the type <code>feat</code> gets released as a MINOR version bump</li> <li>BREAKING CHANGE: a commit that has a footer <code>BREAKING CHANGE:</code> gets released as a MAJOR version bump</li> <li>types other than <code>fix:</code> and <code>feat:</code> are allowed and don't trigger a release</li> </ol> <p>If a commit does not contain a conventional commit style message you can fix it during the squash and merge operation on the PR.</p>"},{"location":"#build-process","title":"Build Process","text":"<p>The CI/CD setup uses Docker build-push Action  to publish container images. The workflow is based on the RaBe shared actions.</p>"}]}