On: Why you should probably be using SQLite

[returningfory2]

I think just running Postgres via the standard Docker image solves most of these issues.

Also an in memory Postgres would be nice, but Docker again gives an easy way of setting up “throwaway Postgresses”.

This all assumes Linux ofc.

[DANmode → returningfory2]

That doesn't sound super friendly for local development env/prototyping when swathes of webdevs literally don't even know what Docker is, today.

[5Qn8mNbc2FNCiVV → DANmode]

I always put a docker-compose.yaml into the repo and in the readme some instructions to install docker and docker-compose and that they should run `docker-compose up`

Works fine for almost any team. Obviously it would be great if they would try to understand it, but it's really not necessary.

Not like most web devs know how most of the tools they use work (Source: All the teams I worked at)

[Too → DANmode]

“docker run -ti -p 5412 postgres”? Easy enough to type on my phone. That downloads and starts everything you need and wipes the data on exit. Ideal for prototyping. If you want to keep the data, add some -v flag or use a compose file as suggested below, even easier.

Devs not knowing docker? Just install docker on their machine and ask them run the command above. One day has to be the first.