| commit | 61f0f85eda302a42b06ccf9c8ff8c7a228d0bf42 | [log] [tgz] |
|---|---|---|
| author | Skyler Grey <minion@clicks.codes> | Sun Jun 09 00:02:53 2024 +0000 |
| committer | Samuel Shuert <coded@clicks.codes> | Sun Jun 09 00:40:11 2024 +0000 |
| tree | 93f8e75a88ca7e74363e4a07bbc773654a6cfa4b | |
| parent | 7d53949f4bc33686951327d629423afdd8b4f11c [diff] |
feat: add headscale Headscale is an open source implementation of the tailscale server. We've written a module that will allow you to easily run it with some basic but sensible options, and set it up for running on a1d1. Change-Id: If67dd498cbe0b0c3c81c66a0216845d0eaf1282c Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/728 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