| From: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
|---|---|
| To: | "Duffey, Blake" <Blake(dot)Duffey(at)noblis(dot)org> |
| Cc: | "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pre-populate pgadmin4 configuration (server, for example) |
| Date: | 2017-12-13 04:54:40 |
| Message-ID: | CAKKotZSKreaQ8ajk=EiW+rqinfc=kN+UReHkD9wCk6K61hYG0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org>
wrote:
> pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’
> certain connection entries (server, port, SSL, etc) for use cases such as
> terminal server/Citrix environments. In our (admittedly limited) testing
> pgAdmin 4 ver 2 offers no such keys to store connection specific
> information. We are looking to switch from 3 to 4 and are hoping to
> ‘pre-populate’ certain connection options to ease the user burden.
>
By default, pgAdmin4 will automatically pre-populate the Postgres servers
which are installed locally but user has to add remote Postgres servers
manually in server list.
>
>
> Thanks in advance.
> Blake
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murtuza Zabuawala | 2017-12-13 05:45:21 | Re: flask again |
| Previous Message | Khushboo Vashi | 2017-12-13 04:35:40 | Re: pgAdmin 4 + python wheel + kerberos |