nextcloud / nextcloud/server

Add a sync option to federated shares

Open
#37,177 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: federation feature: sharing
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.
It is not relied to a problem. I was looking for a way other than scripting to sync photos between servers ( backups ) and i've tried using your federated share feature. I though that it would sync from one server to another but i was wrong. It may not be the case but adding it as optional feature could be interesting for users. Server administrator could prevent this action.

Describe the solution you'd like
I don't know what would be the implementation on the backend.

For the user sharing : there could be a "syncable" toggle that permit/prevent the user receiving the share to sync

For the user receiving the share : a folder option to "sync" and "keep in sync"

  • one sync the current state
  • the other one keep syncing with the remote state

For the administrator :

  • a toggle to permit/prevent share sync

Describe alternatives you've considered
I have considered making client side scripts on my friend server. It's not a problem, just a feature that could be useful for less tech-align users. I've searched for apps to do so and there was none, but I think it could be a great "base" feature

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 names no files, tests, or entry points. Start by investigating the existing federated-share flows for the sharing user, recipient, and administrator. Define the scope and behavior for one-time sync, continuous sync, and administrator permission before identifying the affected code and tests.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.