| commit | c4a6e96c428cf3b8f801a9fcd93a46ce28eba6d4 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sat Feb 17 12:23:49 2024 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Sun Mar 10 02:07:37 2024 +0000 |
| tree | 2b1df600c5953339e1a3bfe069d22d78c0f14423 | |
| parent | 8b4f7b6649e73cda4067109ccb188063b8a3115c [diff] |
Add mosh Mosh is a protocol that allows similar-to-ssh shelling, but with reliability improvements when network connectivity is poor Change-Id: Id1b26e0105e8771de2815ebd2f858b1a5a203fa1 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/399 Tested-by: Skyler Grey <minion@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