For some reason when I had troubles with IPv4 and IPv6 and pgadmin I first
came across this post. For others who face the same: actually the issue has
already been solved, have a look at the enviroment variable
PGADMIN_LISTEN_ADDRESS - more information at
https://www.pgadmin.org/docs/pgadmin4/lates
Thanks - patch applied (with a doc update).
On Tue, Jan 29, 2019 at 6:41 AM Diego Augusto Molina
wrote:
>
> Hi, Dave
>
> On 1/22/19, Dave Page wrote:
> > Hi
> >
> > On Wed, Jan 16, 2019 at 12:41 PM Diego Augusto Molina
> > wrote:
> >>
> >> Here's the patch, sorry for the bad manners.
> >
> > Th
Hi, Dave
On 1/22/19, Dave Page wrote:
> Hi
>
> On Wed, Jan 16, 2019 at 12:41 PM Diego Augusto Molina
> wrote:
>>
>> Here's the patch, sorry for the bad manners.
>
> That effectively reverts the fix committed to resolve this doesn't it?
> https://redmine.postgresql.org/issues/3392
Yeah, it reall
Hi
On Wed, Jan 16, 2019 at 12:41 PM Diego Augusto Molina
wrote:
>
> Here's the patch, sorry for the bad manners.
That effectively reverts the fix committed to resolve this doesn't it?
https://redmine.postgresql.org/issues/3392
Maybe the way to go is to expose the bind address (or some options t
Here's the patch, sorry for the bad manners.
--- entrypoint.sh.orig 2019-01-16 09:38:18.760830943 -0300
+++ entrypoint.sh 2019-01-15 16:43:26.0 -0300
@@ -28,7 +28,7 @@
# Using --threads to have multi-threaded single-process worker
if [ ! -z ${PGADMIN_ENABLE_TLS} ]; then
-exec gunico
