pre-populate pgadmin4 configuration (server, for example)

From: "Duffey, Blake" <Blake(dot)Duffey(at)noblis(dot)org>
To: "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: pre-populate pgadmin4 configuration (server, for example)
Date: 2017-12-12 21:34:08
Message-ID: CY4PR10MB159199B3C4F124570B61C75FF9340@CY4PR10MB1591.namprd10.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

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.

Thanks in advance.
Blake

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Duffey, Blake 2017-12-12 21:35:30 pgAdmin 4 + python wheel + kerberos
Previous Message Dave Caughey 2017-12-11 14:20:02 Re: Wrong db/table listed in "View/Edit Data" | "Filter Rows..." tabs