| commit | d3377400b7bd81cb1d5b62c0463a52438e2330a9 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Thu Jun 06 22:01:26 2024 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Sun Jun 09 00:40:11 2024 +0000 |
| tree | 69ac78d376cf963f64e829a71e8d157ebb9840dd | |
| parent | f4d05f08758eb91e46c5dc718184e01664802158 [diff] |
feat(storage): add impermanence We'll setup impermanence for a1d1 based on some RAIDed together hard drives we have. In doing so, we'll gain the ability to keep some important data persistent while losing everything else. This is also useful when looking for what to backup. Change-Id: I51a9dfcaea46a4a21e601615ddd7288c91effa9e Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/724 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