| commit | f4d05f08758eb91e46c5dc718184e01664802158 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Thu Jun 06 21:25:39 2024 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Sun Jun 09 00:40:11 2024 +0000 |
| tree | 11099f7b39f9d3bada8982335eed10cdf27cb73a | |
| parent | 40ae7a03730c93d3c0c305db39e4ffa04bac710a [diff] |
feat(storage): add raid We'll be using software raid for our impermanence persist drives on a1d1, so we need to add a way to enable it Change-Id: I1f2946b37e5950fe82b906df4ba191097c0d2abb Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/723 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