fix(non-clicks): Ensure all modules start disabled

Clicks wants some modules (our backups, secrets and users) enabled by
default. Auxolotl wants to import our modules, and they don't want any
of this stuff.

Importing modules one-by-one is a potential solution, but is rather
messy given things like impermanence which is depended on in lots of
places. It's much cleaner to know whether the current flake is Clicks
and enable/disable defaults based on that

Change-Id: Icfb6d7bacdfbc31f1904ea4a1b6d6e577b03fa09
Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/802
Tested-by: Skyler Grey <minion@clicks.codes>
Reviewed-by: Skyler Grey <minion@clicks.codes>
7 files changed
tree: ae2672266500eda30d93d73303f873d73dd526b8
  1. .reuse/
  2. .vscode/
  3. lib/
  4. LICENSES/
  5. modules/
  6. overlays/
  7. secrets/
  8. shells/
  9. systems/
  10. .editorconfig
  11. .envrc
  12. .gitignore
  13. .gitreview
  14. .gitreview.license
  15. CONTRIBUTORS.md
  16. flake.lock
  17. flake.lock.license
  18. flake.nix
  19. 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