As a deployment admin, I don't want to setup a wildcard domain to get Coder working. Maybe I don't have ready access to a domain I can use, maybe I just don't want to sign into my DNS provider. Whatever it is, we want to cut as many steps from the deployment of Coder as possible.

I propose we offer a public wildcard DNS service for Coder deployments. The domain name could be structured as<url_id>.<deployment_id>.coder.app and we'd have distinct records for each*.<deployment_id>.coder.app. A URL could look like:bluebunnysurprise.542342.coder.app.

Now, Coder Dev just work out of the box.

Of course, we can let people bring their own wildcard domain as well.

Costs

Since we're just offering DNS and doing no proxying, our bandwidth costs and upper bound cost risk should be minimal.

Apps

coder_apps should flow through the wildcard DNS as well as Dev URLs. Right now, configuring an app's base path can be a frustrating experience. If we can leverage wildcard DNS and use the root path,coder_app configuration becomes far simpler. See#2610 and the docshere for evidence.

TLS

We can use LetsEncrypt to provision a certificate for each wildcard name.