[new package] ddns-go

[GrandDuke1106]

Description

This is a new package. Its upstream is https://github.com/jeessy2/ddns-go.

Automatically obtain your public IPv4 or IPv6 address and resolve it to the corresponding domain name service.

Fixes #

Checklist

• Build rule all-supported completed successfully
• New installation of package completed successfully
• Package upgrade completed successfully (Manually install the package again)
• Package functionality was tested
• Any needed documentation is updated/created

Type of change

• Bug fix
• New Package
• Package update
• Includes small framework changes
• This change requires a documentation update (e.g. Wiki)

[GrandDuke1106]

It's just that Synology seems to be unable to directly change Cloudflare's DNS records. And the logo image is something I "drew" myself.

[mreid-tt]

@GrandDuke1106 found a nicer logo for you and pushed to your PR.

[hgy59]

@GrandDuke1106 please add line breaks at the end of all new text files.

[mreid-tt]

@hgy59 anything further before publishing this? I've installed it, logged in and set an admin password, upgraded it and it seems okay. I don't have a DDNS service myself so I can't test the DNS update feature.

[GrandDuke1106]

@hgy59 anything further before publishing this? I've installed it, logged in and set an admin password, upgraded it and it seems okay. I don't have a DDNS service myself so I can't test the DNS update feature.

at least I have started using it normally

[hgy59]

@GrandDuke1106 is it possible to make the -f (update frequency) and -changeTime parameters configurable?
why not using the defaults?

It seems that it is not possible to configure these values in the config.yml. So for customizing the values, we would need an installation wizard and write the values to a file like installer-variables and to load the values from this file in service-setup.sh.
If we support changing the values at package update, it needs some additional effort.
It is not mandatory to change the values at package update since the file with the variable definitions could be edited anytime.
We should not force the user to edit the service-setup file to change such values, because the changes would be lost at each update.
We should use the default values or make it configurable.

Packages using such an approach are minio, demoservice, kiwix,

[GrandDuke1106]

@GrandDuke1106 is it possible to make the -f (update frequency) and -changeTime parameters configurable? why not using the defaults?

It seems that it is not possible to configure these values in the config.yml. So for customizing the values, we would need an installation wizard and write the values to a file like installer-variables and to load the values from this file in service-setup.sh. If we support changing the values at package update, it needs some additional effort. It is not mandatory to change the values at package update since the file with the variable definitions could be edited anytime. We should not force the user to edit the service-setup file to change such values, because the changes would be lost at each update. We should use the default values or make it configurable.

Packages using such an approach are minio, demoservice, kiwix,

The default value for the -f parameter of this program is 300 (i.e., 5 minutes), and the default value for -cacheTimes is 5 times.

I just want to update the DNS as quickly as possible, even though 5 minutes is already quite short.

I will add an installation wizard so that users can customize -f and -cacheTimes.

[GrandDuke1106]

Currently, with this installation method, upgrading or reinstalling with retaining data will generate an environment-variables.new file. Does this file need to be processed?