How is this still not a thing when the db plays such a central role in Moralis?
just proves to me again that moralis is fine for building prototypes but isn't suitable for production grade applications
Oe, somehow I can feel the sigh of exasperation in your message :s
But yes @Ivan you are right we can do it by connecting to the db outside of Moralis and doing it ourselves, thank you for that.
What I'm saying though is that Moralis does such a great job at making it easy to create a dapp and build a db for it that this feels like the last stepping stone necessary to safely publish to production.
It would save the headache of setting up a job on a server to do regular backups and creating an S3 bucket to save them :)
Actually I must say moralis is taking a large part in our app which is on production phase. It provides a lot, but you must contribute your business with extra tools and development always according to the needs, when you really target production.
I used Mongo DB's Compass and lately, our project manager himself, discovered NoSQL Premium version does more than we needed.
Besides, moralis is for decentral apps, think about your architecture, when and why you really need to manipulate your central db.
I strongly prefer that backup/restore be supported on the platform.
I would also like point-in-time snapshot to be supported