2 ms·
Using nonstandard ports would break the `ssh foo.exe.dev` pattern. This could also have been solved by requiring users to customize their SSH config (coder doe
by CGamesPlay 7mo ago
Using nonstandard ports would break the `ssh foo.exe.dev` pattern.
This could also have been solved by requiring users to customize their SSH config (coder does this once per machine, and it applies to all workspaces), but I guess the exe.dev guys are going for a "zero-config, works anywhere" experience.
- w-ll 7mo ago-p ?
- deleted 7mo ago[deleted]
- hrmtst93837 7mo ago[flagged]
- CGamesPlay 7mo agoSSH configs support wildcards, so if you couple it with a ProxyCommand you can an arbitrary level of dynamism for a host pattern (like *.exe.dev). But yeah, everything is a trade-off.
- KomoD 7mo agoToo bad most SSH clients don't seem to support SRV records, they would've been perfect for this: ;; Domain: mydomain.com. ;; SSH running on port 2999 at host 1.2.3.4 ;; A Record vm1928.mydomain.com. 1 IN A 1.2.3.4 ;; SRV Record _ssh._tcp.vm1928.mydomain.com. 1 IN SRV 0 0 2999 vm1928.mydomain.com. If supported it would result in just being able to do "ssh vm1928.mydomain.com" without having to add "-p 1928"