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.
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.