-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[FEATURE] Data migration from self hosted instance #488
Comments
This is a great idea! Do you have any resources that link to how Sentry achieves this? Would love to learn from a good UX for this feature. Also, from my initial understanding, this feature requires that we do the following first:
|
Hi, so i think my question is related to this ticket. I am looking into running a system like appsmith to build various internal applications for my startup/scale-up. Now we have a very experienced devops team but we dont want to spend time om worrying about databases if it can be prevented. Which is why I was wondering if you might know if i would run into any issues if I try to run appsmith against AWS DocumentDb instead of running a mongodb in a container? What other backup/restore solutions would you recommend for me to look at for appsmith/mongodb? |
Hi @crooy 👋 |
Wow, quick response! Ok, first of all sorry for hijacking this ticket 😞. From your answer I cannot be certain you know what AWS Document DB is so to be certain: AWS DocumentDB is a mongodb compatible hosted database, there are some differences. I guess my question is a lazy one, I can also simply try 🤔 . The thing is, I want to pay for hosted services so I can show an SLA to my product owners. Hypothetically, if I do a daily dump of the mongodb, could i restore the database if i want to go back a week for example? |
@crooy whoops my bad I might be wrong then. I definitely thought it was a new db. 😂 #TIL |
@crooy I haven't tried Appsmith against DocumentDB. In theory, it could work but we can't guarantee longer term compatibility because DocumentDB is always a little behind on features supported by MongoDB itself. Hence, I wouldn't officially recommend it to you. But give it a shot and let us know your experience 😄 . Having said that, incase you don't want to manage databases (who does?), you can either:
|
Thanks! I will let you know in case we try and experience Documentdb! Although you make a good point that mongodb-cloud might be smarter. |
This is now possible with import / export |
@crooy did documentdb work? |
DocumentDB doesn't work for me (tried yesterday with the last version). |
havent tried, sorry.
…On Sat, Jan 21, 2023 at 10:41 PM Christian Musa ***@***.***> wrote:
@crooy <https://github.com/crooy> did documentdb work?
DocumentDB doesn't work for me (tried yesterday with the last version).
—
Reply to this email directly, view it on GitHub
<#488 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGOZBWQTFDJEQ7WUMCIRSDWTRJZHANCNFSM4QTBJYEA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Summary
A user thought it might be a good idea to be able to migrate his data from one ec2 instance to another or from an ec2 instance to our cloud instance
Motivation
Users are initially wary of giving the cloud version their db credentials but over time want to move to the cloud version because it's easier to manage or be able to restore their setup on another ec2 instance incase something un-foreseen happens to their instance
Additional Context
Sentry does a great job with this feature!
The text was updated successfully, but these errors were encountered: