Closed metasoarous closed 5 days ago
@metasoarous Is there a way to fix this issue while using a remote/hosted database? Adding the correct connection params in the .env file does not seem to work (same error as #1751), even with the changes listed in this PR.
+1, it would be amazing to be able to use an external/managed postgres instance
Closing in favor of https://github.com/compdemocracy/polis/pull/1817
The ability to override is important for dev machines which already have postgres running locally/natively on the host machine. An earlier attempt was made to fix this, but failed because the
ports
mapping in the dev overlay file does not change the port the other containers use to access the container, just how the port is exposed to the host system (for utility connection, etc). The fix so that everything internal and external all uses the same port involves setting thePGPORT
setting, so that the postgres container actually uses this port internally, and theexpose
declaration, which ensures that this port is then exposed to the rest of the network.