It would be nice to have the DaCHS server -- dedicated on providing VO services -- in one image, separated from the Postgres server -- dedicated on managing the database itself -- in another image.
The idea is to have it as an (advanced) option, the default behavior would still run all-in-one if an DB-dedicated container is not plugged in. An example of such behavior can be seen in Wordpress image, https://hub.docker.com/_/wordpress/ .
Done. The image are being autobuild at the Hub, branches "postgres" and "dachs" are being used here to keep them all in one place (repo); at the Hub they correspond to tags "postgres" and "server" respectively.
It would be nice to have the DaCHS server -- dedicated on providing VO services -- in one image, separated from the Postgres server -- dedicated on managing the database itself -- in another image. The idea is to have it as an (advanced) option, the default behavior would still run all-in-one if an DB-dedicated container is not plugged in. An example of such behavior can be seen in Wordpress image, https://hub.docker.com/_/wordpress/ .