The mentioned "denokv tool" is a self-hosted backend for Deno KV. So does it mean i need to host a separate Deno KV database which uses the backup from S3? And then update my Deno Deployed app to point to this new DB instead of default DB on Deno Deploy?
If that's correct, then it means i shouldn't really use default DB of Deno Deploy, but instead host DB on my own. And if that's true, then the DB on Deno Deploy isn't very useful, cause i have to still host my own DB anyway.
The easiest approach i found so far is to simply use kview and manually click exportexport to get an NDJSON file. Then i can click importimport and use that NDJSON. simple as that. To automate this process i can use kvtoolbox(the same thing that's used within kview) and run it with CRON.
but this feels weird, i wonder how others are doing backups and restores. Asked also on #deploy™ (here) but no answers as of yet.
Thanks for any hints!
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
D
Deno
Chat about Deno, a modern runtime for JavaScript and TypeScript.