-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rocket.Chat update to new version (Example: Rocket.Chat server 0.28.0 update to 0.44.0 #4734
Comments
@sophornsna are you using the mongo database built into meteor or an external database? |
I am using the mongo database built into meteor. |
Any guide or advice we give will be away from using meteor to run in production. My advice would be to export your database from the meteor mongo, and install rocket.chat using a recommended method. To do this first make sure meteor is running. Then run: It'll dump the database in a folder called dump. Then install mongodb on your system. Please see the mongo section in one of our guides: https://rocket.chat/docs/installation/manual-installation/ubuntu/ Once Mongo is installed restore the data using: Then follow the remainder of the guide on setting up Rocket.Chat. |
After run this command it create a directory /dump/meteor , but it get blank. Any idea to transfer my old data on ( meteor mongo ) to restore to my Production RocketChat (Mongo external database)? |
if you run: |
When I run meteor mongo it is connect. |
@sophornsna try it with out the Like:
See what that gives you |
Thank you so much for your support. Now I can backup database from meteor and I can restore it in my production Rocketchat server. Now I use command node main.js instead command meteor to start up rocketchat. |
@sophornsna great! |
Hi developer,
I am very wonder with update Rocket.Chat to new version. I am using the Rocket.Chat old version by git and I want to update it to new version. I run the meteor to startup Rocket.Chat server.
Thanks,
The text was updated successfully, but these errors were encountered: