commit | f1c352b13bde44d558c1b8f38e9a68951f06680b | [log] [tgz] |
---|---|---|
author | Skyler Grey <minion@clicks.codes> | Fri Apr 19 00:07:44 2024 +0000 |
committer | Skyler Grey <minion@clicks.codes> | Sat Apr 20 00:23:57 2024 +0000 |
tree | 30eb4b3f3fc543cd4e37e5021a07a7c0c1bedef0 | |
parent | 0cebca0104b3bf949070337692be3f9d1ad585a8 [diff] |
Setup a wiki.js instance for TransPlace Similarly to the redis instance, TransPlace is rather annoying to run services on. Therefore, I have offered to run this on nix until such a time as Cleo figures out how to set this up on pterodactyl Change-Id: Iceff9c46e34201968f8e7b097267641499417b57 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/632 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