| commit | 6beb7744fc9741fd2b7937210f9aeb4e9927808e | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sun Jun 09 19:45:06 2024 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Mon Jun 10 17:29:42 2024 +0000 |
| tree | ffc2beaf2e189691734bff51fbcb3a501e3e39a6 | |
| parent | 4d386d1b18de4a8916560703fc5f6554464d40ec [diff] |
feat!: Rename a1d1 -> teal We're calling systems by names that we believe are better for tailscale, and one thing that came up was confusion between different but similar number combinations. As it stands, we'll now be using colors for devices and letters (with their phonetic alphabet words) as areas Change-Id: I8f80042dfe3b9520b33b1063ed9be76ac96a74c9 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/741 Reviewed-by: Samuel Shuert <coded@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