| commit | 7610ce4ed936c67228a388ee4ed91df1f1fcf49f | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Wed Nov 29 19:29:59 2023 +0000 |
| committer | Maddie H <maddie@clicks.codes> | Thu Nov 30 18:11:54 2023 +0000 |
| tree | 16d5f2933680752db8e73c97429907aa1562ab41 | |
| parent | 7e8f572c63db858adc0793c2268cc7d00da55536 [diff] |
Add sliding sync proxy for matrix Sliding sync is a future version of the matrix spec, but the proxy can be deployed while still allowing us to use a non-proxied version. Sliding sync allows much faster client load times, etc. as the client no longer needs to sync everything also: rip out commented/disabled coturn code Change-Id: I9026ed7dcaec961f1bc54469f18f04b68f6e3918 Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/82 Tested-by: Skyler Grey <minion@clicks.codes> Reviewed-by: Maddie H <maddie@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