nextcloud / nextcloud/user_migration
Enable the user to set the target of the export file, e.g. external ressource
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 10
- Avg merge
- 6h 5m
- Merged PRs (30d)
- 12
Description
If the user was able to set the target of the export file, one could directly export to the new instance or at least an external drive - e.g. via external resources. This would also solve the problem that one does always need twice the space to be able to export all the user data. Hence exporting from 450 GB user data from a 500 GB server to a new server with 1 TB space is currently not possible.
For importing one can choose the source already, so one can pick an external storage and there is no need to have twice the space in order to store the export file + unpack its content. For the latter a "consume mode" would be handy, but that's another issue.
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 tracing the existing export flow and comparing it with the import path, where an external source can already be selected. Determine how an export target could point to an external resource and verify that large exports can be written without requiring twice the available server space.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100