| commit | 7337ee55056b596e38d8f25f2d49b230c1801ea2 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sun Dec 03 11:58:17 2023 +0000 |
| committer | Skyler Grey <minion@clicks.codes> | Sun Dec 03 16:27:42 2023 +0000 |
| tree | 32be3367d2e82f92fa87ca0b507d8fa6c5c26dfb | |
| parent | 7610ce4ed936c67228a388ee4ed91df1f1fcf49f [diff] |
Remove richdocumentscode After creating an individual collabora online service (see modules/common/collabora.nix) we don't use richdocumentscode. However, it's still here. This commit removes it to avoiding running a second, useless Collabora server Change-Id: Ic30fca1a32cda0d33134a1339db927ed0bf6371d Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/100 Reviewed-by: Samuel Shuert <coded@clicks.codes> Tested-by: Skyler Grey <minion@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