Hack way to keep syncthing 2.x binary up to date

[kapitainsky]

As for now there is only [Syncthing for macOS v2.0.3+1] of this wonderful program available and in the meantime there were close to 10 syncthing binary releases I felt a bit left behind.

I am reading here and on the forum that there are some less or more important reasons to keep it out of date. It is fair enough but I decided to help myself with a bit of DIY:

1. Close Syncthing for macOS
2. Download the latest macOS binary (syncthing-macos-universal-v2.0.12.zip in time of writing) from https://github.com/syncthing/syncthing/releases
3. replace content of /Applications/Syncthing.app/Contents/Resources/syncthing with content of downloaded zip file.
4. Enjoy latest and greatest

*) Use at own risk. But IMO worst case you just delete all and install original (and outdated) version again. I have been updating my syncthing binary like this for some time now. All works like a charm and having the latest syncthing makes my sleep better:)

[xor-gate]

Thanks for keeping me in the loop about 2.x release train, I had some discussion with the main author of Syncthing and he mentioned when 2.1 hits, its stable enough to be used in production setting. So yes, i'm lagging behind with the v2 and it will forever be a manual step to migrate. So we don't break existing production setups. You can indeed replace the daemon executable under the mentioned path. But keep in mind the signature/digital signage of the Application Bundle will break and it can be marked as untrusted. It's a good hack, but not recommended.

[kapitainsky]

100% agree. It is dirty hack for "brave" and impatient only:)

BTW. Thank you for creating this program. Makes life a bit easier.

[marbens-arch]

Thanks for keeping me in the loop about 2.x release train, I had some discussion with the main author of Syncthing and he mentioned when 2.1 hits, its stable enough to be used in production setting.

@xor-gate Isn't that the opposite of what @calmh said?

Waiting for 2.1, whenever that may be (really a factor of when a new feature triggers the versioning bump), doesn’t necessarily seem like a good criteria to me.

[xor-gate]

You mean the text from post here: https://forum.syncthing.net/t/roadmap-and-deprecation-of-v1-release-branch/24918/4. I run the project on best effort. And needed to catch up on life past 6 months. No offence. But if someone really wants to use v2, for now they are stuck with the supplied versions. I will catch up soon hopefully, and I need to do some writeup how people can migrate manually with two Sparkle Framework updater "appcast" files. It is not as simple as people think it is, or else somebody recreated the project based on native macOS APIs.