Post by @matt@toot.cafe

2025-12-04 23:18 UTC

@polotek@social.polotek.net I think that a lot more personal projects, and even small company-internal projects that don't require 100% uptime/HA/etc., can and should be hosted on just a single Linux server with regular backups. Then run the application in a container if you really want to, but it could just use podman with its systemd integration. And just put the database and files on local storage.

Replies (1)

@evana@hachyderm.io 2025-12-05 01:36

@matt@toot.cafe @polotek@social.polotek.net if the data matters, you probably want something backing up that database. If the data doesn't matter, then just go ahead and lose it. 😁 While backing up a database isn't hard, it's the sort of thing that's easy to screw up and annoying to check/maintain. That's a great thing to offload to a platform (either company managed or from a service). One "cheat" I will do with managed database systems is to use multiple named databases within the same instance, so they all share backups, access control, and billing unit. For a small project, that let's me amortize the effort. For a big project, it's probably a mistake, but formalizing the backup / restore to migrate to a separate database when you got that scale might be a good practice opportunity anyway.

Open ##2300289