alpine-mariadb VS cloudflare-ddns

I currently use the linuxserver nextcloud image with the mariadb image from yobasystems because it's more lightweight than others I've found. Happy to share my docker-compose.yml file if useful. I have been intending to migrate to the official nextcloud image but haven't found a good time to do it yet. I trust linuxserver images enough, they have a good reputation, but I like to be as close to upstream as possible. Mariadb is one example where the arm architecture isn't officially supported. I chose a third-party image rather than built my own because nextcloud was one of the first things I migrated over to docker before I learnt how to build images. Goes to show learning docker does take time :)

Try using this container instead. You can update the A record of your domain to your IP dynamically and use a CNAME for each subdomain so you don’t have to worry about them not resolving when your IP changes.

Can you explain the difference between that and this? https://github.com/timothymiller/cloudflare-ddns

Maybe something like that? https://github.com/timothymiller/cloudflare-ddns

Additionally, I also use cloudflare-ddns for dynamic DNS routing + e2e proxy stuff next to SWAG.

You can use something like [dynamic dns updaters](https://github.com/timothymiller/cloudflare-ddns). They run on the box and when they detect that your ISP has changed your IP will update the DNS records accordingly.

Then you can use cloudflare-ddns to update the domain records if your IP changes, in case you don't have a static ip, similar as duckdns