feat(fava)!: Improve ledger configurability

This contains the following fixes and improvements for fava config:
- Changing the config now takes effect on old files, as well as new ones
- Options have been introduced to allow setting arbitrary beancount and
  fava config, rather than just the title

Change-Id: Ia827ee9646df6b18491a1257ec1a2582e4d8e971
Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/793
Tested-by: Skyler Grey <minion@clicks.codes>
Reviewed-by: Samuel Shuert <coded@clicks.codes>
2 files changed
tree: 207dfecefff250d32a2d7fb37717023382ff18b6
  1. .reuse/
  2. .vscode/
  3. lib/
  4. LICENSES/
  5. modules/
  6. overlays/
  7. shells/
  8. systems/
  9. .editorconfig
  10. .envrc
  11. .gitignore
  12. .gitreview
  13. .gitreview.license
  14. .sops.nix
  15. configure.sh
  16. CONTRIBUTORS.md
  17. flake.lock
  18. flake.lock.license
  19. flake.nix
  20. README.md
README.md

Clicks - Infrastructure

This repository contains system configuration for Clicks's infrastructure.

Config

Config is written using Snowfall lib. It keeps us organized and has some nice features like namespaces.

Systems

Devices are named after colors, areas are named as a letter, with the matching phonetic alphabet word. Areas are generally managed by one member of Clicks, who has full access to all of the servers in that area. If you require help for a specific area you can email admin@clicks.codes and in the subject line include the area you want help for.

SystemDescriptionAddress
tealPrimary Hostteal.alpha.clicks.domains
a1d2Build Serverd2.a1.clicks.domains

Deploying

Deploys are done with deploy-rs, you'll need to be able to ssh into a machine with its hostname (either by a nifty .ssh/config rule or tailscale).

Once you've done that, you'll be able to deploy with

$ deploy .#MACHINE_NAME