Great, thanks. Can you now test it in a container? I think you'll need to
map the file location in the container to the host machine, and then
specify the location in the container (e.g. /pgpass in the example below)
when you configure the server in pgAdmin. e.g.
docker run -p 80:80 \
-e "
Yes Dave it's working as expected.
On Thu, Jun 27, 2019 at 8:16 PM Dave Page wrote:
> Fahar, can you verify that the Password File option works as expected (or
> not) in a non-containerised environment? It should *not* require PGPASSFILE
> to be set (because that's basically what it should be do
Fahar, can you verify that the Password File option works as expected (or
not) in a non-containerised environment? It should *not* require PGPASSFILE
to be set (because that's basically what it should be doing for us).
Thanks.
On Thu, Jun 27, 2019 at 8:27 AM Andrew Coleman
wrote:
> Recently, wh
Recently, while testing my changes to entrypoint.sh in Docker, I noticed
that you cannot import or export passwords via the servers.json file. You
can get around this by setting the PassFile option in servers.json, but
that still doesn't work correctly. For me to make this work, I had to also
set t
