Lock down Postgres and Clickhouse Docker image versions in the Makefile for a consistent development environment

[MaybeThisIsRu]

Bug report

Describe the bug
When I followed the contributing guidelines, and brought up the Postgres and Clickhouse containers as instructed in step one, I noticed the images are not locked to any version at all. This might result in unexpected issues locally as production might be running Postgres 12.x whereas I might have Postgres 13.x locally (for an example).

Expected behavior
Postgres and Clickhouse would be locked to at least the same major version (per SemVer) as the one on production for bringing the local and production environment closer.

Screenshots (If applicable)
On running make postgres:

On running make clickhouse:

[ukutaht]

Thanks @hirusi. I've pinned the Postgres and Clickhouse versions in our hosting repo for the same reason. We should probably use the same in development: https://github.com/plausible/hosting/blob/master/docker-compose.yml

[MaybeThisIsRu]

Thanks @hirusi. I've pinned the Postgres and Clickhouse versions in our hosting repo for the same reason. We should probably use the same in development: https://github.com/plausible/hosting/blob/master/docker-compose.yml

Great! Thanks for pointing that out - I've opened a PR to have specific versions locally.

There's one more improvement we could make -- that is to use volumes for the postgres container. At the moment, I have to sign up fresh on Plausible each time I boot the database container. If you're happy to have that change, I'll open a PR later on.

[ukutaht]

Yes that sounds good as well :)