-
Notifications
You must be signed in to change notification settings - Fork 593
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
www/caddy - Issue tracker for DNS Providers #3872
Comments
I would love to have netcup compiled. :) |
@dMopp Wanne try and add it? I documented what needs to be done. If you get stuck I can help. |
I have compiled Netcup in since it was a bit more complicated, I had to issue an upstream PR too. But now, only the Plugin GUI is left, which is just some copy pasting. |
I would really like to help, but to be honest i dont know where to start right now :O |
It's okay, I will add it next week. It'll be in the next plugin version. |
Hello, |
@un73l I'll evaluate it and if the build checks out I will add it. |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Explain the problem
This issue is for tracking the current state of DNS Providers in the os-caddy plugin.
If you have issues, need to have a DNS Provider added, or have questions, please post that in this issue, don't create a seperate issue. Please note that I don't have accounts to test any of these providers. Following the link to their current maintainer will be a good starting point.
Since the DNS Providers in caddy are a community maintained effort, it is likely that plugins become unmaintained, forgotten, or dysfunct over time. To mitigate the risk of the build of caddy-custom failing, and to make sure there aren't any exploits in the code, a retention policy is enforced.
Policy:
The less DNS providers, the better for the build to make it less bloated. Though there is no other choice, so yeah...~ Adding maintained providers is ok.
🟥 A DNS provider plugin will be removed and not be added if:
🟩 A DNS Provider plugin will be added if:
Compare this list to: https://github.com/caddy-dns
Colors explained:
🟩 - Will stay in build
🟨 - Will stay in build unless errors, though marked for deprecation if no updates are provided
🟥 - Will be removed from build in next plugin version.
Current compile status:
How does the workflow look like to ensure a new DNS Provider plays nice with the rest?
make ports-caddy-custom
The text was updated successfully, but these errors were encountered: