My trusty notebook NAS and homelab
Marty Oehme
4a5a0beca1
Change the inclusion of backup containers so they actually work. They check that restic is enabled globally, and that restic is enabled for the individual stack they belong to. If either of the conditions is not met they do not deploy. This way we can simply enable restic globally with `restic_enable` and by default all stacks will be backed up. But if we want to exclude specific stacks from backups we can do so with the individual `<role>_restic_enable = False` variable. Finally found a good version of doing so with the help of the following medium article: https://medium.com/opsops/is-defined-in-ansible-d490945611ae which basically makes use of default fallbacks instead. |
||
|---|---|---|
| group_vars/instance_system | ||
| roles | ||
| .gitignore | ||
| ansible.cfg | ||
| inventory | ||
| README.md | ||
| site.yaml | ||
Homelab NAS stacks
All the homelab server roles running here. Intended as an (ultimately) idempotent setup, perhaps with ansible preparing the host and the roles.
For now, a simple storage of my docker stacks, transferred from an older NAS system.
Arr stack
Hosts all the pertinent *arr applications, as well as indexer collection application prowlarr, download services, and media management applications jellyfin and audiobookshelf.
Media can be requested through Jellyseerr.
Served through homarr personal dashboard.