-
Notifications
You must be signed in to change notification settings - Fork 24
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
Improvement: Cloudflare deploy production explanation #7
Comments
Docs are super out of date. Looking to fix docs over the coming weeks. |
Is there any way to secure the configuration screen ! as at the moment any one could change my dns configuration ? |
No, they can't. The configuration (which looks like: |
i have deployed a serverless dns to cloudflare and i can access the /configuration url from any wr ! |
You mean, the domain is publicly accessible? You can setup auth, but typically, you don't have to worry about anyone hitting your URL endpoint if you don't advertise it anywhere. Workers today costs $1 per every 3 million to 5 million requests (that's worth ~20 devices worth of DNS queries). If you still want auth, check the serverless-dns readme |
Currently the default cloudflare deployment deploys everything as development with the environment variables editable using the worker UI and never an update.
The text was updated successfully, but these errors were encountered: