| commit | bed35f19b11fe397525d65e6ead86e573b562310 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Thu Jul 04 00:46:44 2024 +0000 |
| committer | Skyler Grey <minion@clicks.codes> | Thu Jul 04 01:56:50 2024 +0000 |
| tree | ef84fad2ff52a3fe1faeab29dde2e0cc196af957 | |
| parent | d7e1acd9d201feb70b31090fa86ad58b9364b282 [diff] |
fix(headscale)!: Rename 'url' to 'domain' This better reflects the value which goes in the option by removing confusion about if the protocol should be included Change-Id: Ib550eb97b96999a733c07915c8738a337546ec52 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/790 Reviewed-by: Samuel Shuert <coded@clicks.codes> Tested-by: Skyler Grey <minion@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