forked from hacc/haccfiles
Nixfiles, for hacc.
6a408db9c1
because gitlab broke websites AGAIN, they are now running on hainich directly While this is only a temporary solution, I think it will be as permanent as they come |
||
|---|---|---|
| common | ||
| desktop | ||
| hosts | ||
| modules | ||
| nix | ||
| pkgs | ||
| .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)