commit | 772dcbbeec5cb971114bcd6433975ff2894997f1 | [log] [tgz] |
---|---|---|
author | Skyler Grey <minion@clicks.codes> | Mon Jun 10 17:14:06 2024 +0000 |
committer | Samuel Shuert <coded@clicks.codes> | Mon Jun 10 17:29:42 2024 +0000 |
tree | e179c2a9ab1091a983ea665e5a530d9d43e8b66e | |
parent | 8ef34818108286e06de0cbd32411715c4ae75e62 [diff] |
fix(tailscale): disable ssh server Tailscale ssh isn't properly supported on the currently released version of headscale, so while it's an excellent idea in theory it doesn't currently make much sense for us to have it on, and breaks SSHing to our openssh ssh servers over the tailnet Change-Id: Iac7039db42da8c05be192d555776f37150195214 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/743 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