| commit | 8ef34818108286e06de0cbd32411715c4ae75e62 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sun Jun 09 19:42:15 2024 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Mon Jun 10 17:29:42 2024 +0000 |
| tree | b58c94619f5d142de8587845dc750623d4c3b588 | |
| parent | 6beb7744fc9741fd2b7937210f9aeb4e9927808e [diff] |
feat(teal): Add tailscale We set up a headscale server, but we did not yet add a client so it isn't possible to use it on the tailnet. Let's do that! Change-Id: I686a6f6d8df2b4a8dd9d47389aacb0bff3abff82 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/742 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