| commit | 44635e2db80522a204cca44ce46e3a9c899653ad | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Wed Oct 25 21:01:42 2023 +0000 |
| committer | Skyler Grey <minion@clicks.codes> | Wed Nov 01 10:00:16 2023 +0000 |
| tree | a98ffb70f6f51e445ccb8c564ec30beb8692099a | |
| parent | a7b38dd1c8c1ee1a3cf6382da5b69a454da587fb [diff] |
Add Coded's nix ssh key Coded has dual-booted NixOS, and generated a new SSH key. This SSH key is resident to his YubiKey so will presumably stay the same unless/until he gets another Change-Id: Ifbf4fc9788d9b7476deb445fa6b956c49961f5d0
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