Behaviour for versioned files on external storage
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
The issue asks whether file-version databases on external storage are migrated and what migration sequence users should follow. Start by verifying the plugin's current behavior, then document the confirmed caveats and procedure; done means users can prepare, export/import, and remap external storage without ambiguity.
Written by the indexing model from the issue text.
Description
First of all: thank you for implementing such a much-needed tool!
I was thinking about using the tool migrating from a NC standalone docker to the AIO docker on an Unraid system. In the old docker, most of my actual user files are mounted as external storage (this is a common practice on Unraid for Nextcloud installations - e.g. look at https://www.youtube.com/watch?v=mOHOcgVMLGM).
Now I know that with v2.0.1 of this plugin, external storages are by default not part of the archive anymore (which I think is in line with the expected behavior). However, I'm unsure about the database for the versions of the files on that storage. Is this migrated? If so, how?
Related to that is the question for me: what is the correct migration procedure if one uses external storage and versioning?
Should I unmount the external (local) storage from the old container first? Should I remap them as external storage to the new container before importing the migration file (I assume)? What needs to be prepared to not completely mess up the database and files?
The point I'm making: is there already documentation available on the caveats etc. when using this plugin together with external storages?
Thank you!
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 11
- Avg merge
- 5h 21m
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from nextcloud/user_migration
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nextcloud/user_migration#1105 ·
Maintainers usually reply within 1 day
-
Comply with instance setting to disable change of user names during importPossibly taken A pull request linked to this issue is open or already merged. Open0. Needs triage bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
nextcloud/user_migration#1188 ·
Maintainers usually reply within 1 day
-
0. Needs triage bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
nextcloud/user_migration#1142 · 5 comments · 9 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
nextcloud/user_migration#1111 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
nextcloud/user_migration#1107 ·
Maintainers usually reply within 1 day
All issues in nextcloud/user_migration
Similar issues
-
good first issue quality
Difficulty 1/5 Under an hour Newbie friendliness 86/100
StudentSuite/awesome-student-resources#554 ·
Maintainers usually reply within 1 day
-
content good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
StudentSuite/awesome-skills-plugins-for-students#297 ·
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 62/100