Embedded database support / SQLite

[JadedBlueEyes]

Is your feature request related to a problem?

Setting up a separate database server can be a bit error of prone or difficult. Ideally users would just have to set up a single service/container.

Describe the solution you’d like

Ideally indicate would support multiple database backends, that you could configure. One of these would be sqlite or another embedded database.

The library used for cache seems to already have support for multiple different backends. The db use throughout the rest of the app doesn't seem to be that complex either, so that could be abstracted over.

Describe alternatives you’ve considered

An all-in-one docker image. Much less of a fan of that, though

Additional context

No response

[eclecticpassions]

I agree with the complexity of creating a MongoDB (no experience with it) to use indiekit fully. I actually couldn't get the {n} token (sequential numbering) working with Mongo and ended up using a longer and unique path/URL name to get multiple photos uploaded on the same day to work.

[paulrobertlloyd]

I also like the idea of using SQLite in place of MongoDB, especially since it’s now included as part of Node.JS. It’s just a matter of figuring out the best approach (do we need an ORM, and if so, which one) and rewriting all the parts that call database queries. And does there also need to be a migration strategy?

Open to suggestions. And if anyone has experience with SQL/SQLite in the context of an Express.JS application, very open to a PR to spike an initial approach!

[JadedBlueEyes]

I haven't done an express app in quite a while now, but I can suggest not using prisma as an ORM, because they don't seem to support automatic migrations. Need to strip it out one of my apps.