Wie Sie sehen, sehen sie nix!
https://docs.hacc.space
stuebinm
16245e830f
This removes the special configuration to make our workadventure useable for the truelove event and reverts it to just run at void.hacc.space without authentication etc. Tbh, not sure if that's actually what we want — do we need a running workadventure instance at all? Or should we just remove the entire container? |
||
|---|---|---|
| common | ||
| desktop | ||
| hosts | ||
| modules | ||
| nix | ||
| pkgs | ||
| services | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| default.nix | ||
| README.md | ||
hacc nixfiles
welcome to hacc nixfiles (haccfiles). this is the code describing our nix-based infrastructure.
structure
default.nix: Entrypoint to the configcommon/: configuration common to all hostsdesktop/: desktop-relevant communicationmodules/: home-grown modules for hacc-specific servicesnix/: sources files, managed with nivpkgs/: packages we built and don't want to upstream
working with the haccfiles
deploy:
nix build -f . deploy.$hostname && ./result switch
$hostname can be replaced with any hostname or group
committing to haccfiles
- Golden Rule: DO NOT COMMIT TO MAIN
- exceptions apply, if you are not sure where to commit, don't commit to main
- split up commits, every commit is one atomic change
- e.g. no big "did some changes" but instead "updated service x", "updated service y", "update service z"
- follow the commit format: "$prefix$place: $change"
- prefix: one of fixup, nothing
- place: one of "modules/$module", "$hostname/service", "common/($place)", "pkgs/$pkgs" or "sources"
- change: describe your change, don't go over the character limit where git starts hiding/wrapping
- Exception: autogenerated messages (merge commits, reverts, etc)