nextcloud / nextcloud/server

Configurable conflict solutions to automate massive cases

Open
#31,665 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage client: 💻 desktop client: 🤖🍏 mobile enhancement feature: dav
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Is your feature request related to a problem? Please describe.
Sometimes tens, hundreds or thousands of files are conflicting from Nextcloud client POV

Describe the solution you'd like
Both server and client should support a policy to solve automatically each case. Server can notify recommended action to client, and client can apply its mandatory behaviour. Server configuration should allow differentiate between clients.

  • Server side policy to recommend each client per each case: a) Ask user (default) b) Client downloads server's content c) Client uploads client's content.
  • Client side policy to apply per each case: a) Ask user b) Client downloads server's content c) Client uploads client's content. d) Apply server's policy (default).

Describe alternatives you've considered

  • Allow user of desktop client to select massively conflicts and trigger action: a) Upload b) Download c) Defer d) Ignore

Additional context
A sysop must have a way to implement Nextcloud infrastructure with unexperienced users, to synchronizations be unattended with conflicts resolutions unattended.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue mentions server and client conflict policies but names no files, tests, or entry points. Start by mapping how conflict handling and client synchronization are represented in this repository and identify the client-side project separately. Done would require an agreed design and coordinated server/client implementation for policy-based conflict resolution.

Written by the indexing model from the issue text.

Assessment

Domain
backend, cloud, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.