| commit | 40ae7a03730c93d3c0c305db39e4ffa04bac710a | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Thu Jun 06 21:22:25 2024 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Sun Jun 09 00:40:11 2024 +0000 |
| tree | 3000ad2b372e57ad4c682545a2d753682bdcbbce | |
| parent | eebf2d2c18bccead9c9596fdac3de7b030ad48d6 [diff] |
feat(storage): erase rootfs on boot We want impermanence so that it's easier to keep track of what state we have on our system, and what we should be rigrously backing up This is the first step towards setting that up Change-Id: I399a7035237f02172180be559c9340faba40af47 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/722 Reviewed-by: Samuel Shuert <coded@clicks.codes> Tested-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