On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake <blake.duf...@noblis.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 >
