| commit | f68685dc7059e31dcd58135137f601cbd881c30a | [log] [tgz] |
|---|---|---|
| author | Samuel Shuert <coded@clicks.codes> | Sat Oct 28 20:07:56 2023 -0400 |
| committer | Skyler Grey <minion@clicks.codes> | Thu Nov 16 22:53:33 2023 +0000 |
| tree | abc11f485cd945c6539adb2e8b4867b6565a4f1b | |
| parent | 8faa2562e0499d7aa68b7a4c2c9e6ad11353567e [diff] |
Move all flakes into modules/ and sep't, create deploy script for a1d2 Change-Id: Ie4d50fb8f16da193195beb139922a366b72b0b0a
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