Skip to content
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

Open
3 tasks done
Monviech opened this issue Mar 26, 2024 · 8 comments
Open
3 tasks done

www/caddy - Issue tracker for DNS Providers #3872

Monviech opened this issue Mar 26, 2024 · 8 comments
Assignees

Comments

@Monviech
Copy link
Sponsor Member

Monviech commented Mar 26, 2024

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:

  • they're unmaintained for too long (like 2-3 years of no updates)
  • they make the build of caddy-custom fail
  • users report errors with the functionality, and they won't be fixed
  • the maintainers ignore issues or pull requests on their provider module

🟩 A DNS Provider plugin will be added if:

  • it's explicitely requested
  • it doesn't make the current caddy-custom build fail
  • it is in the caddy-dns repository and doesn't look unmaintained

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?

@dMopp
Copy link

dMopp commented May 19, 2024

I would love to have netcup compiled. :)

@Monviech
Copy link
Sponsor Member Author

@dMopp Wanne try and add it? I documented what needs to be done. If you get stuck I can help.

@Monviech
Copy link
Sponsor Member Author

Monviech commented May 23, 2024

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.

@dMopp
Copy link

dMopp commented May 23, 2024

I would really like to help, but to be honest i dont know where to start right now :O

@Monviech
Copy link
Sponsor Member Author

Monviech commented May 23, 2024

It's okay, I will add it next week. It'll be in the next plugin version.

@un73l
Copy link

un73l commented Jun 5, 2024

Hello,
Thanks for the work. Could it be possible to have Infomaniak added ?

@Monviech
Copy link
Sponsor Member Author

Monviech commented Jun 5, 2024

@un73l I'll evaluate it and if the build checks out I will add it.

@Monviech
Copy link
Sponsor Member Author

Monviech commented Jun 6, 2024

@un73l Infomaniak and a few more will probably be in next version, build checks out.

#4032

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants