Network UPS Tools container image based on RaBe UBI9 Minimal.
Run it as you please. Not that this image does not generate any automated configuration.
+Run it as you please.
+Note that this image does not generate any automated configuration. You can inject config by putting it into the /var/tmp/nut-config/ directory which gets copied to /etc/nut during startup.
The CI/CD setup uses semantic commit messages following the conventional commits standard. The workflow is based on the RaBe shared actions diff --git a/search/search_index.json b/search/search_index.json index 71046d8..8e1b147 100644 --- a/search/search_index.json +++ b/search/search_index.json @@ -1 +1 @@ -{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"RaBe NUT Image","text":"
Network UPS Tools container image based on RaBe UBI9 Minimal.
"},{"location":"#usage","title":"Usage","text":"Run it as you please. Not that this image does not generate any automated configuration.
"},{"location":"#release-management","title":"Release Management","text":"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.
The commit message should be structured as follows:
<type>[optional scope]: <description>\n\n[optional body]\n\n[optional footer(s)]\nThe commit contains the following structural elements, to communicate intent to the consumers of your library:
fix patches gets released with a PATCH version bumpfeat gets released as a MINOR version bumpBREAKING CHANGE: gets released as a MAJOR version bumpfix: and feat: are allowed and don't trigger a releaseIf a commit does not contain a conventional commit style message you can fix it during the squash and merge operation on the PR.
"},{"location":"#build-process","title":"Build Process","text":"The CI/CD setup uses Docker build-push Action to publish container images. The workflow is based on the RaBe shared actions.
"}]} \ No newline at end of file +{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"RaBe NUT Image","text":"Network UPS Tools container image based on RaBe UBI9 Minimal.
"},{"location":"#usage","title":"Usage","text":"Run it as you please.
Note that this image does not generate any automated configuration. You can inject config by putting it into the /var/tmp/nut-config/ directory which gets copied to /etc/nut during startup.
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.
The commit message should be structured as follows:
<type>[optional scope]: <description>\n\n[optional body]\n\n[optional footer(s)]\nThe commit contains the following structural elements, to communicate intent to the consumers of your library:
fix patches gets released with a PATCH version bumpfeat gets released as a MINOR version bumpBREAKING CHANGE: gets released as a MAJOR version bumpfix: and feat: are allowed and don't trigger a releaseIf a commit does not contain a conventional commit style message you can fix it during the squash and merge operation on the PR.
"},{"location":"#build-process","title":"Build Process","text":"The CI/CD setup uses Docker build-push Action to publish container images. The workflow is based on the RaBe shared actions.
"}]} \ No newline at end of file diff --git a/sitemap.xml.gz b/sitemap.xml.gz index d1ee9a7..249bef3 100644 Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ