Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feat] One-Way Sync Option (on a per-directory basis) #6121

Closed
kn0wmad opened this issue Oct 7, 2023 · 4 comments
Closed

[feat] One-Way Sync Option (on a per-directory basis) #6121

kn0wmad opened this issue Oct 7, 2023 · 4 comments
Labels
enhancement enhancement of a already implemented feature/code feature: 🔄 sync engine

Comments

@kn0wmad
Copy link

kn0wmad commented Oct 7, 2023

I did my best to search the existing issues for this feature, but did not see it. The search filter on GH seems to be awfully liberal. Apologies if I missed a duplicate.

Feature description

Option to sync a directory in only one direction, i.e. from client to NC server.

@kn0wmad kn0wmad added the enhancement enhancement of a already implemented feature/code label Oct 7, 2023
@marcotrevisan
Copy link

Hi,
just curious: in case of the client-to-server-only direction, how would you deal with server-side changes? Your local folder structure would soon become incompatible with the server version and the client-to-server updates won't work reliably.
The only way to make it work (in my understanding of your requirement) is to ensure that a) you're the only user of a server folder and b) your computer's desktop client is the only source of changes for that folder. Seems quite a borderline use case...

On the other hand, having a "read-only" client copy of some folders would be useful for sure in some scenarios, and would perhaps allow for some performance optimizations.

@kn0wmad
Copy link
Author

kn0wmad commented Oct 13, 2023

With a one-way sync, the client would obviously not be concerned with server-side changes. For this use-case, the user would presumably not be making edits server-side, or at least not expecting those changes to sync to the client. For example, I often want to send files to the server, and then not keep them locally. In fact, I want this at least as often as a full sync, as the server has far more storage than the clients do. Hopefully this makes sense.

@sunjam
Copy link

sunjam commented Nov 13, 2024

Duplicate of

@joshtrichards
Copy link
Member

Duplicate of #1090

@joshtrichards joshtrichards marked this as a duplicate of #1090 Dec 3, 2024
@joshtrichards joshtrichards closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement enhancement of a already implemented feature/code feature: 🔄 sync engine
Projects
None yet
Development

No branches or pull requests

4 participants