hacc/haccfiles
8
0
Fork 1
Code Issues 1 Pull requests Projects Releases Wiki Activity
Wie Sie sehen, sehen sie nix! https://docs.hacc.space
209 commits 10 branches 0 tags 21 MiB
SCSS 40.3%
HTML 28.5%
Nix 28%
Scheme 1.6%
Shell 0.9%
Other 0.7%
Find a file
schweby 9770b4089a
sources.json: replace refs with branches 
refs are the old way of referring to what niv tracks for updates
niv actively encourages to switch to branches or tags so this is done
here
2021-04-20 21:39:17 +02:00
common Revert "security: remove hexchen" 2021-03-26 22:04:27 +01:00
desktop remove hexchen from the project 2021-01-25 11:37:34 +00:00
hosts hainich/minecraft: get server.jar via sources.json 2021-04-17 17:19:52 +02:00
modules hainich: init mattermost beta 2021-03-24 22:37:38 +01:00
nix sources.json: replace refs with branches 2021-04-20 21:39:17 +02:00
pkgs pkgs: set jre_headless to jdk11_headless 2021-04-03 21:07:02 +02:00
.gitignore repo: add vim swapfiles to gitignore 2020-11-29 12:53:03 +00:00
.gitlab-ci.yml ci: remove instantiate stage 2021-02-22 09:41:15 +00:00
default.nix default: unclutter by using a recursive attrset 2021-01-22 19:26:05 +00:00
README.md readme: add golden commit rule 2021-01-20 18:47:57 +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)