commit | 08758a6f58bb93fc1af2a295ca451dae6f66ab3f | [log] [tgz] |
---|---|---|
author | Skyler Grey <minion@clicks.codes> | Mon Oct 09 07:35:09 2023 +0000 |
committer | Skyler Grey <minion@clicks.codes> | Mon Oct 09 07:39:03 2023 +0000 |
tree | 60a6e209835172397108dc7aa91eac5dc027512a | |
parent | 0e05d26279ddd69359eac4262c70e5d07b7e6b80 [diff] |
Add gerrit Gerrit is a service which provides code review via "changes" (commits) which you can continually amend, viewing the diffs between them in a very similar way to <https://graphite.dev/> (which is awesome but too expensive for Clicks to justify). We hope it'll provide some better structure than the GitHub workflow we have been using Still TODO (in a followup change): - The bazel build for the oauth module is horrible and introduces tips from <https://zimbatm.com/notes/nix-packaging-the-heretic-way>. This is generally considered a bad thing. We should change this - Gerrit cannot yet send emails Change-Id: I1393b2ae5a1efe049ea2170de46070d8789a2e3a
To deploy these files to our server we use deploy-rs. If you've got a flakes-enabled nix installed on your system you can run
nix run github:serokell/deploy-rs
You can also install deploy-rs to your profile, at which point you'll be able to run
deploy
Secrets are stored in SOPS and deployed using scalpel.
If you have a service which needs to store secrets in its config file, please set systemd reloadTriggers and restartTriggers to automatically reload/restart the service whenever the configuration changes.
It's notable that changing the secrets will not trigger a reload/restart of the service. If you want to update the secrets without updating the rest of the configuration you currently need to manually restart the service. It's possible that this could be solved by using systemd paths to watch the files (see https://superuser.com/questions/1171751/restart-systemd-service-automatically-whenever-a-directory-changes-any-file-ins) but this is not a priority