| commit | e6a8c71bc86360235a5dc5e82e6fad871cb9599e | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sat Jun 22 01:41:28 2024 +0000 |
| committer | Skyler Grey <minion@clicks.codes> | Thu Jul 04 01:56:50 2024 +0000 |
| tree | b6f97b6568b1a3f9071c98e4155220e909036f1f | |
| parent | 02c195ef030ebc92ab8ab02ea5db35a4e3cbecc6 [diff] |
feat(flake): Add unit testing Change-Id: Idc9bbca0e752b21a5293e2ad4819da9af42ca8ca Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/782 Tested-by: Skyler Grey <minion@clicks.codes> Reviewed-by: Samuel Shuert <coded@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