commit | 2b9b1fed5b4b4d63afb5dd4adf47c204cf0019a3 | [log] [tgz] |
---|---|---|
author | Skyler Grey <minion@clicks.codes> | Sun Dec 31 16:12:02 2023 +0000 |
committer | Samuel Shuert <coded@clicks.codes> | Sat Jan 06 12:10:46 2024 +0000 |
tree | e75b37703f6d7b18fa40e8e56a9e9855344321a2 | |
parent | 896e92891c8c1627500b3bf3805676feb696e96f [diff] |
Add turquoise.fyi as an ACME mail domain Turquoise.fyi is owned by MostlyTurquoise, who we are hosting mail for. Adding it as a mail domain will make us fetch certificates for it. Change-Id: I4271f2efcff944d51f9bf4774d9e3b6ed6a1548d Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/207 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