| commit | 4d386d1b18de4a8916560703fc5f6554464d40ec | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sun Jun 09 16:05:44 2024 +0000 |
| committer | Skyler Grey <minion@clicks.codes> | Sun Jun 09 18:49:58 2024 +0000 |
| tree | 2eb19f75ad81c9cb8abe0d4cfc3191527a3278e8 | |
| parent | 61f0f85eda302a42b06ccf9c8ff8c7a228d0bf42 [diff] |
feat(tailscale): Add base domain as search domain Doing this will allow access to other people's servers with "foo.username" rather than "foo.username.<base>". The likelihood of this causing trouble is minimal, but we may prefer to be careful to avoid allowing names that might conflict with existing TLDs Change-Id: I7d73a037bd999cfb94556a63d97387275e582195 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/739 Tested-by: Skyler Grey <minion@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