| commit | 37f9097d4b89dc75a39dc7ef17161f993a830d98 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sat Jun 22 14:30:56 2024 +0000 |
| committer | Skyler Grey <minion@clicks.codes> | Thu Jul 04 01:56:50 2024 +0000 |
| tree | a978535396453e71c19b54572fabc11cf7e38b66 | |
| parent | e6a8c71bc86360235a5dc5e82e6fad871cb9599e [diff] |
fix(tailscale)!: Remove protocol from login server Having the login server have http/https means that we don't have complete parity with our headscale service, which uses the login server for both the url and the module. Given we believe you should be using only https for tailscale servers anyway, we haven't added an option to change this Change-Id: I81189487bd19777e41dc4e88f2800758242e7698 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/783 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