revert: fix(non-clicks): Re-export dependencies

In change I433d34395b0449de17af2dea2a8a3138c1ff6dba, we moved to
re-export dependencies in a hope that it would let people easily import
our modules and avoid evaluation errors

Unfortunately, if someone already uses our dependency, importing again
doesn't only import a single copy, as would happen in languages like
Python, rather it imports it a second time, and fails due to duplicate
declarations!

This makes containing our dependencies in our exports untenable

Change-Id: I4e5d15e1f436e4140bcb27e4ed15542b4f5812af
Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/809
Reviewed-by: Skyler Grey <minion@clicks.codes>
Tested-by: Skyler Grey <minion@clicks.codes>
1 file changed
tree: b7cd44a72797d874610d9793c0f6a445c42f1933
  1. .reuse/
  2. .vscode/
  3. lib/
  4. LICENSES/
  5. modules/
  6. overlays/
  7. packages/
  8. secrets/
  9. shells/
  10. systems/
  11. .editorconfig
  12. .envrc
  13. .gitignore
  14. .gitreview
  15. .gitreview.license
  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