Migrate to using a wildcard certificate

[basil (Basil Hendroff)]

@francislavoie

I don’t think map is optimal here because it involves placeholders for the proxy upstreams. There’s some things that aren’t possible when the reverse_proxy handler needs to resolve its upstream addresses from placeholders.

What’s interesting is that @matt uses the map directive for wildcard subdomains in the wiki article Serving tens of thousands of domains over HTTPS with Caddy and doesn’t use the handle block. Is there a subtle difference that I’m not understanding between the two approaches?

@francislavoie

it’s not possible to have more than one log per site block in the Caddyfile unfortunately, so you can’t split your logs into multiple files when using this pattern. This is a limitation of the Caddyfile adapter at the moment

Noted.

@francislavoie

In your map approach, you used {hostname} but this wouldn’t work as-is because that would give you the full hostname, not just the subdomain. You would need to use {labels.3} to get the actual subdomain (i.e the 0 indexed 4th host label, starting from the right).

OK. I see what I’ve done wrong.

@francislavoie

You’ll probably want to move www.dance.com.au into the same site block if you want it to use the wildcard cert. You can do this with another handle block similarly to the snippet above.

Noted.

@francislavoie

You might not need to do that though since you’ll only have tls defined once if you use a single site block with handle blocks.

Noted.