| commit | 77897517f1c68c7dab878e0f66b1ba082c7ca1de | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sun Dec 10 00:03:38 2023 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Sun Dec 10 00:34:05 2023 +0000 |
| tree | 5d93d9a8f4b7242b4f0902f68a746223df731156 | |
| parent | 180ff19acc19834f902b57d2d08cd81e68046987 [diff] |
Fix taiga image uploads Previously there were 2 problems with taiga image uploads - The env variables for the domain were set incorrectly - In the front container, the media and static folders were in the wrong place Change-Id: I232c0263cf7b8ea209870fc4d1a98ecd066bc60a Signed-off-by: Skyler Grey <minion@clicks.codes> Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/182 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