[Feature] Add support for external archiver-plugins (to support using borg-backup)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 272
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
With plugins taking over the actual "archiving" I think it might be possible to still use a lot from the UI and integration with Nextcloud, but provide for a solid backup-funktionality in the backend. Using borg-backup things like encryption, deduplication and compression are already handled by a performant and proven stable tools. Left to this plugin would be nextcloud-specific things like sqldumps, metadata, deciding which folders to backup or the UI-part.
Borg offers functionality to access and manage backups, to list or prune backups, if need be even "fuse-mount" a particular backup. Externally all backups appear like "full backups" although they are stored efficiently, even encrypted, and handled transparently to the application.
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
Start by mapping the current backend archiving flow, the Nextcloud integration, and the UI responsibilities described in the issue. Define the scope and boundaries for external archiver plugins, including how Borg-style encryption, deduplication, listing, pruning, and mounting would be represented; done means the plugin contract and affected integration points are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100