You'll probably need to select some other network share folders as output folder, and possibly create a new share to make sure the permissions are pristine and not messed up. Packages for DSM 7.0 : Java Installer ( java-installer-dsm7.spk) FileBot ( FileBot-dsm7.spk) FileBot Node ( filebot-node-dsm7. By default, Synology NAS probably wouldn't give you write access to it's primary mount point. So instead of automation I have to backtrack on a scheduled task and change the permissions each time to move the files out of that folder. FileBot packages for Synology DSM 7.0 are in beta and available for testing. FileBot packages for Synology DSM 7.0 are in beta and available for testing. The way this FileBot package operates is it needs the folder and files to have an Owner of admin instead. I run FileBot Node on the NAS and am running into permission issues with that particular folder, because after Syncthing performs the transfer it changes the folder and files Owner to syncthing. The FileBot Node server-side service is indeed running on 127.0.0.1:5452 but that's just an internal implementation detail, and the internal node service is notably only accessible from the DSM host itself, and exposed to the network only via the Synology DSM WebUI akin to how a reverse proxy works. When files get put into the Completed DL folder they are transferred one-way back to the NAS. The “Client” for Syncthing is running inside a VM running Linux Mint for various other tasks, but only watching one SEND ONLY folder - Completed DL. adminDS216play: filebot -version FileBot 4.9.0 (r6980) / OpenJDK Runtime Environment 13.0.1-BellSoft / Linux 3.10.105 (arm) java. Rewrite Synology DSM integration for DSM 6.2.4 and DSM 7 Rewrite QNAP QTS. Installed latest filebot with bought licence. Wait if something else comes up too in the meanwhile. Contribute to filebot/filebot-node development by creating an account on GitHub. EDIT: No FileBot Node release in the near future since there arent any other changes that warrant a release. One Shared Folder is allowed access using the Group SC-Syncthing and it is called DL. The amc script itself remains unaffected, for now, unless theres some good general unrelated to Synology reason to exit 0 for 'did nothing but successfully so'. Syncthing is running on my Synology NAS as the “Main Server” for my Network. I have been using Syncthing for a while now and have a question about permissions.Īllow me explain how my setup is being run:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |