MerginMaps / MerginMaps/media-sync
Versioning data on Mergin server when synced with media-sync
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 8
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
From the user point of view, this tool can save them a lot of storage on their quota. But on our server, we keep versioning the data and even if we move the data away, still the storage is taken up with the previous version of the data.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, entry points, or acceptance criteria. Start by tracing media-sync's synchronization and server-side storage/versioning flow, then clarify how moved media should affect retained versions and what storage behavior will count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100