RE: pre-populate pgadmin4 configuration (server, for example)

From: "Duffey, Blake" <Blake(dot)Duffey(at)noblis(dot)org>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>, "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 13:33:14
Message-ID: CY4PR10MB1591921216964EBEEF98DB5FF9350@CY4PR10MB1591.namprd10.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

We’d be happy to try that Dave (assuming someone could give us a couple sentences on how to do so)

From: Dave Page [mailto:dpage(at)pgadmin(dot)org]
Sent: Wednesday, December 13, 2017 8:31 AM
To: Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org>
Cc: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>; pgadmin-support(at)lists(dot)postgresql(dot)org
Subject: Re: pre-populate pgadmin4 configuration (server, for example)

On Wed, Dec 13, 2017 at 1:16 PM, Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org<mailto:Blake(dot)Duffey(at)noblis(dot)org>> wrote:
Is there any way to create a custom .db file in the users AppData folder that could simulate what the registry keys did in the version 3?

Right now the only option would be to take a freshly created file, and use the sqlite client to execute the appropriate SQL inserts on it to add the servers.

I have been toying with the idea of writing a small command-line tool (and maybe UI tool?) that would let you import and export server definitions, but haven't got round to it yet.

From: Murtuza Zabuawala [mailto:murtuza(dot)zabuawala(at)enterprisedb(dot)com<mailto:murtuza(dot)zabuawala(at)enterprisedb(dot)com>]
Sent: Tuesday, December 12, 2017 11:55 PM
To: Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org<mailto:Blake(dot)Duffey(at)noblis(dot)org>>
Cc: pgadmin-support(at)lists(dot)postgresql(dot)org<mailto:pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: pre-populate pgadmin4 configuration (server, for example)

On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org<mailto: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

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Stephen Frost 2017-12-13 15:20:21 Re: pre-populate pgadmin4 configuration (server, for example)
Previous Message Dave Page 2017-12-13 13:30:58 Re: pre-populate pgadmin4 configuration (server, for example)