nextcloud / nextcloud/nextcloudpi
suggestion: custom DynDns provider
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
hi @nachoparker,
i have one suggestion that you are able to use any dyndns provider with following configuration at your config page:
update-url: example: (http://www.ddnss.de/upd.php?user=&pwd=&host=&ip=&ip6=)
domain name: example: (test.ddnss.de)
user: example: (test)
pasword: example: (test)
update intervall: example: (10)
advantage would be to use nearly any provider without actively supporting each of them.
We just need an Update-URL function.
Thanks again for your great work!
Contributor guide
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
No files or tests are named. Start by locating the existing DynDNS configuration and update entry points in the repository, then determine how provider settings are represented. Done means users can configure an update URL, domain, credentials, update interval, IPv4 address, and IPv6 address for an arbitrary provider.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100