| commit | 619aa3ca3e17a17a2e8e35af9790cce821614af4 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Tue Nov 21 20:28:50 2023 +0000 |
| committer | Skyler Grey <minion@clicks.codes> | Wed Nov 22 19:47:17 2023 +0000 |
| tree | 7699bc1db346a5a5da0d0ccd9f527be54b2dd6a6 | |
| parent | e6a5a914da20829306ab48a08f17c98d1f610279 [diff] |
Fix most nextcloud setup warnings - Inside nextcloud, we previously had several warnings about defaults not being set for regions, email not working due to a missing base URL and caches that were too small - This commit fixes all warnings except one about the database being used for file lock handling, which I think we will need to setup redis to solve Change-Id: I54d25a85cc291f3ba3fe84a9972e772f82d678a3 Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/29 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