![synology syncthing synology syncthing](https://www.nagoya88.net/adminsblog/assets_c/2019/06/Syncthing-thumb-320x320-8819.png)
SYNOLOGY SYNCTHING HOW TO
Below is a summary of how to join the framework and what package center does for you: If anyone feels a strong need for an updated SPK, I will quickly take care of it upon request.To reduce security risks, we now provide a framework to run packages with a lower privileged "package user" instead of root. Just trying to keep the effort for SynoCommunity low. I’ve been doing that for the last couple releases and will keep monitoring for when incompatible changes might warrant a new SPK. So usually a new Syncthing version gets pulled as part of other changes in the packaging. Regarding upgrades, the SynoCommunity folks are quite busy so if an app updates itself internally, there is no pressing need to keep publishing SPKs. Got stuck with DSM internals there, however. from Let’s Encrypt with auto renewal) get reused for Syncthing. I was working on integration with the system certificate store, so that the installed certificates (e.g. An icon on the “Desktop” linking to Syncthing’s own web GUI. Predefined rules for the DSM integrated firewall.
SYNOLOGY SYNCTHING INSTALL
An install wizard IIRC asking some permission stuff and educating about the sc-syncthing group for ACL management. In the end, I think that’s an advantage.Īnother point for the SynoCommunity version is better integration with the DSM UI. However, I understood what the intention with the Kastelo version is to do the releases with the SPK and not through the GUI. The good thing in connection is that after the SPK installation, the GUI can then be updated to the latest version, currently v1.3.3.
SYNOLOGY SYNCTHING UPDATE
Unfortunately, the SPK update cycles are much to long and not connected to the releases, v1.2.2 is still current. The Kastelo version has no advantage over the version of SynoCommunity with regard to the package center, since this also has an SPK for the package center. It remains to be seen how close these updates are to the releases.
![synology syncthing synology syncthing](https://forum.syncthing.net/uploads/default/original/2X/0/05e0d5ba79de5b2e467ab74ecd57cd7fea196d76.png)
With the Kastelo version, an update of the SPK is required, I assume a new SPK will be displayed in the package center. In the version of SynoCommunity, updates are made directly via the GUI, as usual. No user mapping has an advantage or disadvantage over the other. In any case, these two user assignments do not appear to have any influence on the known synchronization problems. In contrast, for “internal system users” (Kastelo) each individual main directory has to be edited separately, which means considerably more effort. The “sc-syncthing” group can be easily assigned to the various main directories in the Control Panel as “Local Groups” (SynoComm.). I cannot find any relevant difference between “internal system users” and “local groups” at the moment. This now only as a hint, if you think about a change, you should take into account that everything has to be set up again afterwards.Īfter setting up and first testing of the Kastelo version compared to the version of SynoCommunity, I have two advantages for the version of SynoCommunity. The update itself was successful, but then the folder and device settings were all gone (!), which is equivalent to a new installation. I was careful and did the update on a Test Synology. As v1.2.2 is currently up to date for the SPK and v1.3.3.3 for Kastelo, an update is displayed. The next step is to be careful when storing the package source “ ” if the package from SynoCommunity is installed at the same time. But I suppose this can be changed in the options, I will check it. What I saw in difference, the version of Kastelo can not update via the release channel, that is deactivated. What are the advantages of the “internal system user” over a group and is it above a group? That would be very interesting for me. My question would therefore be whether the above effect would be gone. However, it always happens with the main directories that messages appear, such as “error while traversing /volume1/abcxyz: permission denied”Īn “internal system user” is stored in the version of Kastelo. “sc-syncthing” is stored as a group, which can be assigned relatively easily for the main directories.
![synology syncthing synology syncthing](https://forum.syncthing.net/uploads/default/original/2X/4/402a1efb59e58cdbc7840dc406829249ad4068d6.png)
I have the version of SynoCommunity in use for years and it runs very well.įrom time to time I have problems with permissions. The question is, in fact, what would be the benefit of the Kastelo version.