| commit | 8c85404aa44f980263456ce6e7e52e9160e70c59 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Wed Oct 25 17:31:57 2023 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Wed Oct 25 14:22:10 2023 -0400 |
| tree | ad7352b0c29f89f6537f70c219c487f24d85de21 | |
| parent | e15f5aaf10e69c8080aab5e28f5c351ee90fd941 [diff] |
Add a .vscode with formatting rules We have a .editorconfig, but this is not respected over live share. Adding a .vscode fixes the issue Change-Id: I147c4ad158a8af97f8936bf230ed9dea4e998e6f Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/164 Tested-by: Samuel Shuert <coded@clicks.codes> Reviewed-by: Samuel Shuert <coded@clicks.codes>
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