Interesting, background sync was completely broken on the new beta timeline for me. I had to open the app, and disable then reenable sync every time I had new photos.
I'm back on the old version because it's basically 100% reliable.
Correct yeah, you'd still need a way on the host to check if the mount is ready though before starting the service. Or you could just do a fixed delay time.
For subdirectories it's more complex as each application needs to be configured properly too, so you'll need to go into transmission and tell it what subdirectory you're using.
Or switch to subdomains as that just works without any extra config, and still let's you use one port for everything.
You should be able to modify the docker service to wait until a mount is ready before starting. That would be the standard way to deal with that kind of thing.
For what it's worth when you set up your site on cloudflare you get to choose how strict you want security to be and what URLs it applies to, or just disable it and use it only as a CDN. Or even disable routing entirely and use it only as your DNS.
It would be nice if they were more clear that enabling some features might block legitimate users though.
Nah there's no debugging here, just edit the config file on the host where it's stored exactly like you would on a native install.