commit | c4ab9c60cc47277ecd2ac72a30c8b55146c5cc6b | [log] [tgz] |
---|---|---|
author | Skyler Grey <sky@a.starrysky.fyi> | Thu Aug 08 21:01:44 2024 +0000 |
committer | Skyler Grey <minion@clicks.codes> | Thu Aug 08 21:25:44 2024 +0000 |
tree | b7cd44a72797d874610d9793c0f6a445c42f1933 | |
parent | 38d4a3ecc05b057a0f09f261d5ad38ce1c364e24 [diff] |
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>
This repository contains system configuration for Clicks's infrastructure.
Config is written using Snowfall lib. It keeps us organized and has some nice features like namespaces.
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.
System | Description | Address |
---|---|---|
teal | Primary Host | teal.alpha.clicks.domains |
a1d2 | Build Server | d2.a1.clicks.domains |
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