feat(gitea): LFS over ssh, direct LAN route at home
LFS_ALLOW_PURE_SSH keeps LFS objects on the ssh connection instead of ROOT_URL via neptun. On terra/titan, ssh to git.mgaction.town goes straight to jupiter when it answers on the LAN. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -61,6 +61,20 @@ in
|
||||
};
|
||||
};
|
||||
|
||||
# At home, ssh to gitea goes straight to jupiter instead of out to neptun and
|
||||
# back over the tailnet; away, the probe fails and the public route applies.
|
||||
# The alias matches the existing known_hosts entry (same gitea host key).
|
||||
# LFS rides the same connection via LFS_ALLOW_PURE_SSH (services/dev/gitea.nix).
|
||||
programs.ssh = {
|
||||
enable = true;
|
||||
enableDefaultConfig = false;
|
||||
matchBlocks.gitea-lan = {
|
||||
match = ''host git.mgaction.town exec "${pkgs.netcat}/bin/nc -z -w1 10.0.0.20 2222"'';
|
||||
hostname = "10.0.0.20";
|
||||
extraOptions.HostKeyAlias = "[git.mgaction.town]:2222";
|
||||
};
|
||||
};
|
||||
|
||||
# direnv + nix-direnv: lets per-repo devShells (e.g. /mnt/hdd_01/dev/repos/Tome's
|
||||
# flake.nix) auto-load in the shell AND in Rider via its "direnv
|
||||
# integration" plugin, instead of every dev repo needing its own
|
||||
|
||||
Reference in New Issue
Block a user