-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Backing up development installation data? #635
Comments
Go into the |
Thanks @geekgonecrazy, it's there. 👍 |
no problem. Good info to know when working with this. Might need to put together a wiki article for tips like this. |
I have an issue which is related to my original question here. It's about migrating the users (etc) to a new location. Steps:
That's where it goes bad:
Perhaps I am doing this the wrong way. Do anyone know of a better way to migrate old data for usage on a new instance? |
Sorry to be pushy :) but would anybody have a good idea on how to accomplish what I've tried to do, as per what I briefly [tried] to outline in the comment above? |
can we add an option under admin to backup?? locally? or remote |
@RocketChat/owners can anybody help out with this one? Is it possible to move data from one install to another? |
@k0nsl did you create a replication group on the vps? Because just copying alone won't do the trick. While running meteor if you do:
You'll notice its running on port Pretty sure you have to use the same replSet. I'd honestly advise using mongodump connecting to it and dumping it. Then do an import. |
To export the data from a development DB, you should use http://stackoverflow.com/questions/22020580/how-to-connect-mongodb-clients-to-local-meteor-mongodb |
I'm running R.C in development mode by following these instructions:
What I cannot seem to figure out is, where is the data stored and how would one go about backing it up? I am specifically refering to user registration data. That's what I wish to backup.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: