pg_ssl_init

"[email protected]" <[email protected]>
Newsgroups gmane.comp.db.postgresql.devel.general
Message-ID <[email protected]>
In May of last year (2019), I set up pg_ssl_init on gitlab:

https://gitlab.com/osfda/pg_ssl_init

And announced it on this list:

https://www.postgresql.org/message-id/1621ef11-f246-8519-018d-57ba36ecc16b%40osfda.org

pg_ssl_init is a set of python3 scripts that configures SSL certificates 
to insure SECURE remote pgadmin access. To do so manually is a multistep 
process, fraught with many opportunities for a mistake to be made and 
numerous hours to be wasted troubleshooting it. It has been tested on 
popular Linux distros (debian, Ubuntu...), though it is written to _try_ 
and work on Windows [But I would need a willing tester to get in touch 
to confirm that and fix any compatibility issues for Windows...] It 
works great on Debian 10.

For some VERY odd reason, while the stub of the repo was still visible, 
the files of the repo stopped appearing on gitlab -but the repo was 
marked public (?)

I marked the repo private, saved the settings; then marked it public.
Behold: all the files then reappeared.

I guess gitlab is finding out that it's hard to find good technical help!

If anyone reading these posts referring to pg_ssl_init has any problem 
in future accessing that repo, get in touch at the contact page at 
osfda.org. Should gitlab let us down again, at that juncture I will 
figure out another amenable open source code hosting solution that's not 
corporate...
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.