The experimental flag that allows to override the go-sync server from the UI was merged to Nightly, but with the caveat of enforcing HTTPS usage for most deployment scenarios: brave/brave-core#28463
I assume you use some reverse-proxy in production with go-sync, so it would be useful to at least mention that in the README that TLS is basically required or, ideally, add optional caddy/nginx setup to docker-compose.yaml for home-brew TLS with Lets Encrypt.
The experimental flag that allows to override the go-sync server from the UI was merged to Nightly, but with the caveat of enforcing HTTPS usage for most deployment scenarios: brave/brave-core#28463
I assume you use some reverse-proxy in production with go-sync, so it would be useful to at least mention that in the README that TLS is basically required or, ideally, add optional caddy/nginx setup to
docker-compose.yamlfor home-brew TLS with Lets Encrypt.