change time zone to UTC

advantages:
- avoids daylight savings time issues
- generally UTC is used as a default in languages so it's easier to work with than a different local time
- we don't much care about what time it physically is by the server when using it

Change-Id: Ifa5db94f1504cfbf34fa3fea975f61106432ca0e
Reviewed-on: https://git.clicks.codes/c/Clicks/NixFiles/+/165
Reviewed-by: Ash Franks <pineafan@clicks.codes>
Reviewed-by: Skyler Grey <minion@clicks.codes>
Tested-by: Ash Franks <pineafan@clicks.codes>
1 file changed
tree: c6fbc226a981c3b5534c241fc68dab454d7e9ed9
  1. .vscode/
  2. default/
  3. homes/
  4. host/
  5. modules/
  6. packages/
  7. secrets/
  8. services/
  9. variables/
  10. .editorconfig
  11. .envrc
  12. .gitignore
  13. .gitmodules
  14. .gitreview
  15. .sops.yaml
  16. flake.lock
  17. flake.nix
  18. LICENSE
  19. README.md
README.md

Clicks' NixFiles

Deploying

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

Updating secrets

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