Set up a dedicated SODAR Core dev docker compose repo?

[mikkonie]

This is something I've been wondering in the past weeks. For 99% of the tiime, sodar-docker-compose can be used for SODAR Core development. That's what I do: I just use a separate database for SODAR and SODAR Core.

However, there are exceptions and we're seeing one right now. Once I merge #880 into dev, which I'm just about to do at the time of writing, the SODAR environment will cease to work with SODAR Core. This is because #880 bumps the minimum version of Postgres to v12, which is not supported by the enviromnent, as it is not supported by the current iRODS image. Work on the iRODS image and the environment is ongoing: see bihealth/irods-docker#16, bihealth/irods-docker#18, bihealth/sodar-docker-compose#34 etc.

However, it's a question whether the effort to set up and (especially) maintain a new repo is worth it. As said this is a rare occurrence and an easy way to get around is to e.g.:

• Clone sodar-docker-compose
• Comment out everything except Postgres and Redis
• Run that
• Create database and user manually in Postgres

Or just run Postgres and Redis on bare metal if that's you're thing..

Comments are welcome. I guess I just accidentally gave anyone reading this instructions for a workaround anyway :)