kunsi/bundlewrap
1
0
Fork 0
Code Issues 2 Pull requests 1 Releases Activity
config management repository for all servers operated or managed by me
2270 commits 7 branches 0 tags 22 MiB
Python 88.5%
Perl 6.3%
Shell 4.2%
HTML 0.7%
PHP 0.1%
Go to file
Franzi 59fd245a3f
add dynamic node attribute for last apply 
so we can check if something has changed in the repo since the last
apply
2023-09-01 06:16:09 +02:00
automatix automatix/upgrade_debian_bullseye: do zfs another way 2023-05-20 11:47:39 +02:00
bundles bundles/php: add php8.2 2023-09-01 05:54:54 +02:00
configs bump netbox-dump 2023-03-29 18:19:17 +02:00
data remove htz-cloud.luther 2023-08-04 08:07:41 +02:00
groups move mail from rx300 to carlene 2023-09-01 05:55:27 +02:00
hooks add dynamic node attribute for last apply 2023-09-01 06:16:09 +02:00
libs nodes.py: demagify toml nodes 2023-07-13 20:28:28 +02:00
nodes add dynamic node attribute for last apply 2023-09-01 06:16:09 +02:00
scripts scripts/passwords-for: ensure keys are strings 2023-05-20 14:07:25 +02:00
.editorconfig add home.switch-rack 2023-03-26 15:58:29 +02:00
.gitignore .gitignore: ignore more stuff 2021-10-07 18:25:34 +02:00
groups.py add error_context() to groups.py and nodes.py 2022-02-07 06:57:58 +01:00
Jenkinsfile Jenkinsfile: remove isort check, because it behaves differently between venv and non-venv mode 2023-05-20 07:44:23 +02:00
nodes.py nodes.py: demagify toml nodes 2023-07-13 20:28:28 +02:00
PORT_MAP.md rename bundle:gitea to bundle:forgejo 2023-08-02 16:37:48 +02:00
README.md README: add system naming 2023-05-20 15:00:07 +02:00
requirements.txt hedgedoc new release 2023-06-04 23:17:55 +02:00
users.json nodes/htz-cloud.pirmasens: add user autojenkins 2021-08-27 21:31:10 +02:00

README.md

kunsi/Bundlewrap

Central Config Management Repository for all servers operated or managed by me. May also include some dummy nodes, for example for deploying websites onto shared webhosting.

bw test runs according to Jenkinsfile after every commit. Build Status

automatix

Ensure you set bundlewrap: true in your ~/.automatix.cfg.yaml.

system naming

All systems should be named after their location and use.

For example, influxdb hosted at hetzner cloud will be htz-cloud.influxdb.

The only exception to this are name servers, they are named after demons in fiction.