| commit | 083b1e3bd3313b2aff348bf69229e615aacdf3c8 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Mon Nov 20 18:48:02 2023 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Mon Nov 20 18:52:01 2023 +0000 |
| tree | 7aa3cb6ab5e00737f30b8a6b035120490353a00e | |
| parent | 22428b0d31a9de020ff5ab50c863578fbb6c8766 [diff] |
Enable Mjolnir Mjolnir is our moderation bot for matrix. It was disabled when the server went down, but now the server is back up we should have it again Change-Id: I4e8d3377d1c0916c3afba32a0489e1fbd2c5e74c Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/21 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