| commit | f08a619e8d421f042238209b45f1155447ece283 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sat Jun 01 23:55:20 2024 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Sun Jun 09 00:40:11 2024 +0000 |
| tree | 08df975c6ecf18c863202878174037e7a219047f | |
| parent | f992821aff2b60221368d1619a88b33db05a05f5 [diff] |
feat(a1d1): init Co-Authored-By: Samuel Shuert <coded@clicks.codes> Change-Id: Iaf1499b8cde6d3f6bdb024374f6830d582006aeb Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/720 Tested-by: Samuel Shuert <coded@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.
a stands for "area", d stands for "device". So for example, a1d1 is device 1 in area 1. 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 |
|---|---|---|
| a1d1 | Primary Host | d1.a1.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