Open joshmoore opened 6 years ago
It's a feature! https://github.com/ome/omego/pull/30/commits/3b16ece4ecea1b47b9e56f66b50a90c2e38975cc
Open an issue against omego if you think it should be changed
What do you think about working around it here?
Are the expectations for omero-server-docker different from omego to justify this? If so then we can change it here, if not we should change omego.
Well, minimally, omero-server-docker knows if it's initializing or upgrading, no? https://github.com/openmicroscopy/omero-server-docker/blob/master/60-database.sh#L41 If that's the purpose of the feature in ome/omego@3b16ece to prevent inadvertent upgrades, then it seems like it could be valid to have the docker override in some cases.
Note: this is fairly nasty. We might decide to strip issue numbers from snoopy comments. cc: @sbesson
In an attempt to deploy PG+OMERO with the minimal characters on the CLI, I tried:
(This repo uses "omero" rather than "postgres" as a default, but that would be a breaking change)
I get this error:
We could consider this an
omego
bug (in which case, happy to migrate this), but another option would be to overrideomero.db.name
with the default ofomero
here as is done with omero.db.host. See https://github.com/openmicroscopy/omero-server-docker/blob/master/60-database.sh#L12