-
Notifications
You must be signed in to change notification settings - Fork 889
SSH config should not suggest or use .dev
TLDs
#3143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The suffix is the name of the agent. All of our example templates use coder/examples/templates/docker/main.tf Lines 68 to 88 in 5e32468
Perhaps dev isn't the best name for agents, but since conflicts would be rare and the workaround is a small edit to the template, I think we can close this issue. |
Maybe we can rename the agent in the default templates instead? |
The
.dev
TLD is not reserved, and havingcoder config-ssh
overridecoder.workspace-name.dev
can conflict with real domains.For example if my coder instance was hosted on
coder.aaaa.dev
, and I had a workspace calledaaaa
, I can no longer SSH to the server that hosts the Coder instance.The frontend and
coder ssh-config
should therefore not use.dev
after the workspace name.The text was updated successfully, but these errors were encountered: