Support migration to another server (through user_migration app)
Open
Nobody has claimed this yet.
enhancement
Needs triage
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
When moving to another Nextcloud instance it would be great to keep my chat history. So ideally the chats are stored in the export created when using the migration app!
Question: This is easy for note-to-self or public chats, but what about user chats?
- I suggest to make the other users guest/anonymous users with their name set as the visible user name.
- perhaps, on import, some day - mapping users would be nice. But for a private user that makes little sense. When migrating multiple users as admin (currently not really a feature!) this will be needed.
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 locating the user_migration app's export and import flow for Nextcloud Talk data. Determine how note-to-self, public, and user chats are represented, then define and verify what preserving chat history and handling users should mean during migration.
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
- Needs clarification
- Newbie friendliness
- 25/100