accepting connections from CNAMEd domains to our worker
I’m writing a multitenancy app and some customers want their custom domains to point to their subdomain at
this mostly works fine except i need to add it to wrangler config (or the dashbaord) every freaking time!
is there a way i can avoid having to add those?
Options already considered:
- writing an admin endpoint (and frontend) that automatically adds this using some cloudflare API. this will be undone upon each deployment as wrangler.jsonc takes precedence and overwrites the dashboard stuff
- using a wildcard for the whole domain (not possible)
Will i have to bind these to my deployments, altering the wrangler config file inside github actions to include the list of current custom domains and then deploying it? this seems very counter intuitive and flaky
inploi.appthis mostly works fine except i need to add it to wrangler config (or the dashbaord) every freaking time!
is there a way i can avoid having to add those?
Options already considered:
- writing an admin endpoint (and frontend) that automatically adds this using some cloudflare API. this will be undone upon each deployment as wrangler.jsonc takes precedence and overwrites the dashboard stuff
- using a wildcard for the whole domain (not possible)
Will i have to bind these to my deployments, altering the wrangler config file inside github actions to include the list of current custom domains and then deploying it? this seems very counter intuitive and flaky
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942Members
Resources
Similar Threads
Was this page helpful?
