-
Notifications
You must be signed in to change notification settings - Fork 1
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
Sqlite backup/restore or backup method - Fermyon Cloud #36
Comments
Maybe spin command that can download my sqlite file? No-ops-db means: "I am lazy. You do my ops for me" not there is no(body) to ops. :-) |
Would love to see this, it makes recommending the inbuilt db very hard |
Fermyon uses Turso behind the scenes. It would be nice to expose their Point-in-Time Recovery feature. As mentioned above, it's very hard to switch to your SQLite offering for a serious project without any kind of backup mechanism. |
Hi everyone! You can execute SQL statements through the CLI using the
Note that the Having said that, because applications have access to the SQL database, it is possible to write a WebAssembly component that will dump your database to a file for you. @karthik2804 wrote a program a while back that provides a web CLI to a SQL database attached to the application. It is most likely out of date, but it could be used as inspiration. I would imagine cron trigger support would be very useful for periodic backups to external systems as well. Out of curiosity, when y'all are asking for periodic backups, where would you expect that data to be stored? Would something like a point-in-time-recovery feature work for your use case, or do you need the ability to export all data to an external source? |
It's a feature request.
I would like to request periodic database backups or database snapshots. It doesn't have to be fully automated, such as recovering from backups through a fancy UI, but I would like a method that I can request through Fermyon, and for Fermyon to perform database backups and recovery for any incident, disaster, or even in the event of a global catastrophe like WWIII.
The text was updated successfully, but these errors were encountered: