forked from hacc/haccfiles
Nixfiles, for hacc.
stuebinm
011196f875
note that this ALSO disables the security alert features of mattermost [1], which would send us alerts in case of security updates for our current mattermost version. I have disabled it since it would send information about our instance (including e.g. the current number of active users) to mattermost every 24 hours. Since we now essentially maintain our own set of mattermost packages, I recommend at least some of us subscribe to the mattermost release blog [2], and manually update the mattermost sources in `/pkgs/mattermost` as required (I have done so already). The release blog is also available as an rss feed [3]. [1] https://docs.mattermost.com/administration/telemetry.html#security-update-check-feature [2] https://mattermost.com/blog/category/releases [3] https://mattermost.com/blog/category/releases/rss |
||
---|---|---|
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)