start dev ckan in parallel

[wardi]

One day our ckan container might be fast enough to start using db/postgres/redis before they are ready. Today is not that day.

Starting the dev environment now launches the db, postgres and redis containers in parallel, waits for them all to be ready then launches the ckan container. This takes a while.*

real    1m32.681s
user    0m20.008s
sys     0m0.333s

If we launch all containers in parallel we get a running ckan in much less time.*

real    0m48.344s
user    0m8.595s
sys     0m0.186s

This could result in an error if ckan starts accessing the database too early, so this change has only been applied to the docker-compose.dev.yml file for now. For such a large improvement I think it's worth considering.

FIXME this could be made reliable by checking for the container status inside the ckan container.

* both measurements include an ~11s shutdown time

[kowh-ai]

Nice, rudimentary testing, no failures of the CKAN container

[wardi]

Unfortunately this creates an issue where docker compose run doesn't bring up the required containers, sending a fix in #142