60-database.sh: Support omero.db.port

[joshmoore]

When running on a non-standard port, it's currently
necessary to create a redirect image using socat in
order to have the database upgraded. Longer-term it
may be easier to delegate this logic to pgpass.

[manics]

What are your thoughts on the structure of the config in this image? Is the combination of env-vars + support for config files (and the interdependency between them) a problem e.g. as in #17? Should it be modified or completely refactored? Or do you think it's an acceptable compromise?

[joshmoore]

I understand what you mean from the other PR that this is getting somewhat unclean, but I don't have a clear idea of how we would fix it. If you have something you've been wanting to see happen, happy to have it spelled out. (Sorry if I'm missing something)

At the moment, I do think that this and gh-17 are somewhat acceptable compromises, or at least, I would much prefer to not wait on a breaking change since I'm now working around in various places:

  redirect:
    build: redirect

FROM centos:centos7
RUN yum install -y socat
ENTRYPOINT socat TCP-LISTEN:5432,fork TCP:host:5433

which is not a nicer compromise.