I take it that it is a settled fact that NextCloud devs. cannot be persuaded to add a âone-way syncingâ feature to the official NextCloud desktop syncing app (âNextCloud Filesâ), and this thread is not attempting to wake up any sleeping dogs. What can those of us who need this feature use though? Again, what I need is some app that has, by-and-large, the same features as the official NextCloud app PLUS one-way syncing (desktop to NextCloud cloud). As far as I can tell, rclone ainât it. Note that it should preferably be open source, and ideally already packaged as Flatpak, or Docker image or the like.
There is no such thing like âone-way-syncâ⊠depending on the direction what should happen with new/deleted files? If you speak about scheduled snapshots/copies it is possible to do such task using webdav and curl (or GitHub - j4m3z0r/davsync: DavSync: like rsync, for WebDAV)
Thanks, looks nice for P2P, only I already have a personal cloud that I went to great lengths to build. Also, they seem to have deprecated the Docker image, which is a shame. Finally, while I may be able to cram the RPM onto my system (ClearLinux), I am not sure if TrueNAS takes RPMs.
One-way sync scenarioâFolder F of computer A is one-way synced with folder FC of computer C (the âcloudâ):
All changes in folder F are automatically replicated in FC, including deleted files. (Nice-to-have option at this point: delete file from F without deleting from FC. (Deleted F files to be renamed to something else in FC.))
All changes to files in FC that originate from F and have the same names as their F counterparts to be automatically replicated in F.
Any files in FC that do not come from F (or originate from F files but were deleted from Fâsee ânice-to-have optionâ above), to be excluded from syncing.
The crucial requirement is that syncing happens in (almost) real time, hence the âautomatic(ally)â attribute. Can Cron jobs be triggered by changes to the F folder? Any change to the content of F needs to be immediately propagated to FC; periodic backups ainât cuttinâ it, as often as they may be.
Whenever people here ask about one-way sync, I always wonder what their actual use case is, and whether there might be a better way to do what they are trying to achieve, or whether Nextcloud is even the right tool for the job
And no, I donât mean the technical description of the process that you described here, I mean the actual use case. What actual real-world problem are you trying to solve with this rather complex process?
Is it about normal files that you work with day-to-day? is this meant to be some backup concept? is it about a kind of autouload of files that are read by a scanner, camera, auto-generated by some tool�
The real-world problem is precisely the problem that one tries to solve using two-way sync ⊠except one very important difference: my Nextcloud cloud is 16T, while my local HDD is 512G in size. The Nextcloud box culls files from 4 other LAN boxes.
Unfortunately, if you are on Linux, this is still âexperimentalâ, which means that only the âbarbonesâ variant using placeholder files is implemented. It does work though.
Could there be a solution whereby you set permissions on some local folders such that the sync down to the desktop can only write into certain areas and not others?
Even without virtual files, you can choose which folders youâd like to sync. I use like this a few working folders, where I have files that I currently work on. Other stuff I only sync temporarily:
