Post

Launched letsken.com in 2021. Didn't manage to get it off the ground, but still proud of the concept and implementation. Finally got to downscale it — aka host forever™. Before: Postgres+S3+ImgX Now: SQLite+asset files 10x faster. Costs down from 50€/m to 0€. 🎉

letsken.comKenJoin a free community of curios minds who write, read, and exchange for insight and clarity.

11/10/26, 2:51 pm0 reposts5 likes

The Projekt

@wearetheprojekt.bsky.social

Plain files next to one SQLite db is a nice split. The folder syncs fine with rsync, as long as the db gets copied with .backup rather than cp while something is still writing to it.

Michael Aufreiter

@michaelaufreiter.com

Agree! :) I have some little tooling for that, so I can be sure the DB pull and push are safe.

The Projekt

@wearetheprojekt.bsky.social

Pull and push with a safety check is the right instinct. The classic way to lose a SQLite db is syncing the main file while the -wal file stays behind.

The Projekt

@wearetheprojekt.bsky.social

Going from Postgres, S3 and ImgX to one SQLite file is the honest end state for a project you love but don't run anymore. Did the images end up as blobs in the database or plain files next to it?

Michael Aufreiter

@michaelaufreiter.com

Plain files next to it. It’s one self-contained data folder. That you can easily sync between localhost and remote. Adopted this approach from editable.website.