DNS automation feature (optional)

[xd-Park3rr]

Small idea: the README says everything is automated except adding the DNS record. For users who manage DNS through Cloudflare, this could potentially be automated too using the Cloudflare DNS API, either from the Developer CLI or a GitHub Actions workflow with a scoped Cloudflare API token.

It probably makes sense to keep the current manual DNS step as the default, since DNS providers vary and users may not use Cloudflare. But an optional “Cloudflare DNS automation” path could make the setup even closer to fully automated.

[tjementum]

Hi...

I've never used Cloudflare, so I would not know. Originally I also planned to make PlatformPlatform multi-region (US, EU, AU, etc) where the DNS entry would point to the cluster. So e.g. cocacola.platformplatform.net would point to US cluster, and lego.platformplatform.net would point to EU cluster. In my previous job we used Azure DNS, so when a tenant was created it also created a DNS record.

It's very likely that we could do the same with Cloudflare, but that would require a secret in the setup (API key), which I don't like, espcially not to a DNS server. Azure DNS can be controlled using Managed Identities, so that would be safer.

But anyway, DNS is too big a change if you ask me. As you say diffrent users use diffrent DNS.

All that said, I probably should look at Cloudflare, and get CDN, which is currenly missing from PlatformPlatform. So maybe someday when I get to it :)