Is there any more specific guideline to setup my own releasesURL thingy so that my remote sites that doesn’t have internet access can update via my private sector?
I’ve tried update a json file manually and run on a web server but I just don’t know what info is require, the setup on both the source and the syncthing client.
I noticed that the url is a description, but is it necessary? how will the client determine the path for the update package?
also, how to config the new discovery server, I changed the port on the client but I don’t see any traffic on the discovery server.
Syncthing have a notice says: “Global discovery: unsupported scheme”
url in release.json is supposed to point at the archive, not another json. The only reason you see json when you are opening it in a browser is because your browser hasn’t sent the right header. If it had, accessing the asset url would start a download.
We’ve already explained this twice, and we’ve pointed at a link that explains it as well, and yet you are still doing the wrong thing.
Given we’ve helped you out setting this up (and can help you further if you have issues), you could be a good citizen and contribute a guide in the documentation repo, in return.
The json format it read may have issue on more than one version tag, at least mine’s don’t work if I stack more than one version it says it can’t find the release information instead
recommend keeping the version list to the minimum as everyone tailor for their own usage.
(since you own upgrade server mostly are private sector limit your own network to specific version you control)
The multiple assets should run without problem but the one I tested are only windows files, plus I didn’t test on both 32bit and 64bit versions
I think the usage in the doc only need a small correction: show the url in file format so other people may understand it more easily.