deleted by creator
deleted by creator
thank you, just subsribed
It matters only if “the docker hosts external IP” your dns resolves is a public IP. In that case packets travel to the router which needs to map/send them back to the docker hosts LAN IP (NAT-Reflection). With cgnat this would need to be enabled on the carrier side, where you set up the port forwarding. If that’s not possible, split-DNS may be an alternative.
If “the docker hosts external IP” is actually your docker hosts LAN IP, all of that is irrelevant. Split-DNS would accomplish that.
Are you hosting behind NAT / at home? If so, you may need to enable NAT reflection on your router.
Yeah the files are stored in blocks. It helps deduplicating and for syncing partial files/change. If your concern is just with being able to copy the files away, there is seaf-fuse, which lets you mount it as a local filesystem: https://manual.seafile.com/extension/fuse/
If you only want online file storage and sync, you may want to try Seafile. It’s a lot faster and has been rock solid since 10+ years for me. Not viable if you need some of the many nextcloud exentions though
I’m surprised no one mentioned ansible yet. It’s meant for this (and more).
By ssh keys I assume you’re talking about authorized_keys, not private keys. I agree with other posters that private keys should not be synced, just generate new ones and add them to the relevant servers authorized_keys with ansible.