Wie Sie sehen, sehen sie nix! https://docs.hacc.space
 
 
 
 
Go to file
hexchen c36eb51ff4 Revert 43d36bb3d7
This is a partial revert, reintroducing hexchen to the project.
As it turns out, I am still quite invested in the project and require
frequent access to the nix-based infrastructure.
2021-02-11 18:59:10 +00:00
common Revert 43d36bb3d7 2021-02-11 18:59:10 +00:00
desktop remove hexchen from the project 2021-01-25 11:37:34 +00:00
hosts Revert 43d36bb3d7 2021-02-11 18:59:10 +00:00
modules sources: removed immae-nix 2021-02-10 23:48:18 +01:00
nix sources: updated sources 2021-02-10 22:53:55 +00:00
pkgs sources: removed immae-nix 2021-02-10 23:48:18 +01:00
.gitignore repo: add vim swapfiles to gitignore 2020-11-29 12:53:03 +00:00
.gitlab-ci.yml complete restructure of haccfiles 2021-01-10 23:53:41 +00:00
README.md readme: add golden commit rule 2021-01-20 18:47:57 +00:00
default.nix default: unclutter by using a recursive attrset 2021-01-22 19:26:05 +00:00

README.md

hacc nixfiles

welcome to hacc nixfiles (haccfiles). this is the code describing our nix-based infrastructure.

structure

  • default.nix: Entrypoint to the config
  • common/: configuration common to all hosts
  • desktop/: desktop-relevant communication
  • modules/: home-grown modules for hacc-specific services
  • nix/: sources files, managed with niv
  • pkgs/: 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)