NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Adding DNS challenge provider Openprovider
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
What provider would you like to see added to NPM?
Openprovider (https://www.openprovider.com/, https://www.openprovider.eu/)
Have you checked if a certbot plugin exists?
Yes: https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_openprovider.sh
Ps. In https://github.com/acmesh-official/acme.sh under dnsapi and deploy there are lots of providers. Wouldn't it be possible to add them all at once (by letting NPM internally use acme.sh with all providers supported)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how Nginx Proxy Manager currently handles DNS challenge providers, then compare that flow with acme.sh's dnsapi/dns_openprovider.sh. Define the integration scope and verify that a certificate can be issued using Openprovider DNS before considering the work done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100