Linkding backups (with a sidecar and S3)

I've started using Linkding1 for storing links in a more curated and deliberate capacity. I have Raindrop which is basically just a mess now, but it's easy to navigate when there's lots of things. Linkding isn't designed that way however, so I'm being cautious. Whatever my usage(s), there is one concern: backing up the data. There's a couple of ways to do this. The first would be some calls via the REST API to build something that could be imported. Too much effort. The sceond was to manually backup through the export function on the settings page. Ick. The third and final option boils down to what was conveniently written in the docs. Since I'm using Linkding in SQLite mode, the 'full backup' option sounds the nicest. It just involves running a command on the container and then moving the data somewhere. Dead simple, unless you're running it on something like Kubernetes, which I am. My plan is fairly simple: Run the 'full backup' command on a cron Send the data to some S3 bucket…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town