Home
Tip
you can ignore this page
Question
no, like really, it's just my random notes
Abstract
Stanley chose the door on his left ðŸ˜
Note
at this point I kinda just wanted to see how many times I could nest these
-
tl;dr; wtf is the karo-stack?
-
how it works
-
why is this the best solution?
-
architectural principles?
- dry? kiss? idempotent, Principle of least privilege (so no fancy webui's), no unnecessary abstractions, well documented/easy to read, privacy by default (some of these might be also about how we pick the stacks), like stable, healthy community, performant and memory safe language,
-
architecture layout
- git, debian, preseed, ansible, rootless docker, traefik, oidc, justfile
TODO
- add note about dhcp for the homeserver
-
add note about the local hostfile entry (e.g. 192.168.0.142 karo-stack) OR adding local addresses to your DNS records
-
why store the vault in git? convenience and versioning, the version of your vault and it's variables will always align with the version of your playbook.
-
allow port 8000 on your firewall
-
how to sync your karo-stack fork with upstream
-
docker should only be managed via ansible, unless a stack was manually created on the server
misc
moving git files