4 ms·
Oh ok so you still have a "dynamic" site that is database driven, but that database is read-only and stored in a pre-generated sqlite file that is deployed with
by mattlondon 3y ago
Oh ok so you still have a "dynamic" site that is database driven, but that database is read-only and stored in a pre-generated sqlite file that is deployed with the rest of the site assets?
I don't want to piss on your parade here - perhaps I just don't get this pattern - but isn't this all of the downsides of a dynamic site but without any of the benefits? You are still running slow server side stuff that relies on doing per-request database stuff and all the complexity and security headaches that go along with it (upgrading PHP or Wordpress or whatever), but with none of the benefits of server side functionality and databases (i.e. it is all read-only).
- simonw 3y agoI talk about the benefits of the approach in quite some detail here: https://simonwillison.net/2021/Jul/28/baked-data/#benefits-of-baked-data https://simonwillison.net/2021/Jul/28/baked-data/#benefits-o... - does that help clarify?