| commit | 1886112a480cc3efba265d54ece827e4f5d4bd38 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Wed Oct 25 21:05:54 2023 +0000 |
| committer | Skyler Grey <minion@clicks.codes> | Wed Nov 01 09:58:42 2023 +0000 |
| tree | 4c11f2c0c1938e65808ae491e812303da243344e | |
| parent | aa1aeacfb669bce5ca4bd12dd2152a765a3bde7f [diff] |
Remove deploy dependence on Coded's computer When we deploy, nginx resolves all of the hosts that are in its config. Unfortunately, we were using the mDNS address for Coded's pi and PC so this was dependent on them being up. This commit changes Coded's PI and PC to be in our /etc/hosts file. A supporting change we have made is making these IPs static on the router Change-Id: Iefffe3a4100b8af6eab4548cf38a85109a826283
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