commit | f7eb4ae98b7ec9d6d23a703051b3475740410b36 | [log] [tgz] |
---|---|---|
author | Skyler Grey <minion@clicks.codes> | Mon May 06 12:38:44 2024 +0000 |
committer | Skyler Grey <minion@clicks.codes> | Thu May 30 08:59:55 2024 +0000 |
tree | 40c0caec9fb11242ddaa865320c8f949212f69a5 | |
parent | 50bbc8f50325d0f0cd7fc2096a66c4eb1663d4d9 [diff] |
Add wikijs for Aux As part of the infra and docs teams for Auxolotl, we've decided to host their wiki for them. This was difficult for a few reasons - They do not use Cloudflare, so our standard https certificate provisioning will not work - They do not want our automatic www subdomains - We already run wiki.js for TransPlace, and are not able to take that down. Nix doesn't allow us to add multiple wiki.js instances alongside each other - This is not permanent, so we want to make it really easy to move to another server at a moment's notice, for example we don't want to tie it in to our postgres server As a mitigation for these - We override our normal ACME configuration. This forces cloudflare by default. We have added an "ugly hack" to avoid it forcing cloudflare for aux - We update helpers to add a "specific" domain, i.e. do not add www aliases - We use a nix container to host the wiki.js and another postgres server Change-Id: Iecead03467f2b4a958d83cc6f92a8a0304323e35 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/682 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