commit | fca18044656596f3925793eea4f6d58c6eb5638f | [log] [tgz] |
---|---|---|
author | Skyler Grey <minion@clicks.codes> | Tue Oct 24 19:17:27 2023 +0000 |
committer | Skyler Grey <minion@clicks.codes> | Tue Oct 24 15:20:39 2023 -0400 |
tree | 0516d363c537f198931cc76d9c1a592673f0a52e | |
parent | ad397882758c8f6841674e8d3aa20ee1c4207bbf [diff] |
Change the default config so gerrit rebases We don't want merge commits, and we would like gerrit to rebase so that we get trailers like the Gerrit-Reviewed-On trailer. Here are the advantages of REBASE_ALWAYS: - Adding trailers (unlike merges or fast forwards) - Cares about dependencies (unlike cherry pick) - Does not introduce merge commits (unlike merges) - Does not require manual rebasing the majority of the time (unlike fast forwards) Change-Id: If94f39c85be48f7fb3aa2138ae60fc3a5f9d4834
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