RocketChat / RocketChat/Docker.Official.Image
transfer data from a dumpfile to a new instance of rocket chat
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 337
- Forks
- 228
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 5
Description
Hello, I have a rocket chat server (v 5.2.0) running on docker container and then backed up data using: docker exec db sh -c "mongodump --archive" > db.dump
I created a docker-compose file, that runs a new instance of rocket chat and MongoDB, then restored the dump file using: docker exec -i db sh -c "mongorestore --archive" < db.dump.
After the docker-compose startup, even when the logs show data transfer was successful, I'm always redirected to the default setup wizard, I looked into it and found i needed to add OVERWRITE_SETTING_Show_Setup_Wizard=completed in the environment, but even then, no data is displayed, it just asks me to log in, the credentials were wrong and I had to create a new user, and even then it's the default rocket chat interface with none of my rooms, channels, custom css...
How can add the data from a dumpfile of a previous rocketchat server to this new one running using docker-compose?
Thanks
Contributor guide
No contributing guide indexed for this repository
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 with the docker-compose configuration, the db.dump file, and the mongodump/mongorestore commands described in the issue; compare the new container setup with the Rocket.Chat 5.2.0 source instance and inspect the startup logs. Done means the restored instance shows the previous users, rooms, channels, and custom CSS instead of the default setup wizard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, mongodb
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100