commit | 896e92891c8c1627500b3bf3805676feb696e96f | [log] [tgz] |
---|---|---|
author | Skyler Grey <minion@clicks.codes> | Fri Dec 22 23:49:10 2023 +0000 |
committer | Skyler Grey <minion@clicks.codes> | Sat Dec 23 19:36:17 2023 +0000 |
tree | 928e9a124532a8ee92b28f47635b3d4da5cfd491 | |
parent | 6f9047dd82732299e68ea68425a99165e91890b0 [diff] |
Fix or reduce overly verbose logs and warnings - The nginx server names bucket was too small, this has been increased - Nextcloud had too high of a log level, this has been decreased - Matrix had a warning due to using the default matrix.org keys. This is fine so has been ignored - A special *evaluation* warning for you: we previously used an old option name, by virtue of some strange behavior in inheriting system config that I do not fully understand. Regardless, we can fix this by filtering out the dead option name Change-Id: I97c517073fb76caed1d000290fd1fad15000057f Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/189 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