Replies: 4 comments 2 replies
-
Hi @pc-dok , thanks for reaching ! This depends on the variation between configurations. $ tree
.
├── ldaprc
├── server1/
│ ├── .env
│ └── ldap2pg.yml
├── server2/
│ ├── .env
│ └── ldap2pg.yml
.
.
. ldap2pg 6.1 (unreleased) will load |
Beta Was this translation helpful? Give feedback.
-
hi etienne ok, is a bit more clear now, but what looks like a .env file than? have you a short example? maybe i write you my env. Postgres Server 16.2 Sorry for that many questions, but i am absolut newbie in this ldap2pg and my thinking is, that i can handle all my postgres servers than from one central mgmgt server! regards |
Beta Was this translation helpful? Give feedback.
-
something like this you mean? POSTGRES_USER="someuser" |
Beta Was this translation helpful? Give feedback.
-
ok, i found out now how i can connect to the other servers over export from the correct PG* ENV Variables. I only now get this error: 15:13:30 DEBUG Closing Postgres global connection. database=test what does this mean? regards |
Beta Was this translation helpful? Give feedback.
-
Hi all
I am wondering if i am the only one, but for me it is not clear how i can use ldap2pg on a central server in our environment, where i have let say, for every postgres server a yaml config. so that i can manage all postgres server from this server. so i struggeling in the creation of the yaml config, to find out, where i must add my servers, so that ldap2pg know, where he must go. LDAP is clear for me, but where i define the remote postgres servers? is it something with DSN or so. Is there a example how to connect to remote postgres servers? sorry for asking, but in the example, i dont find this point!
regards
franco
Beta Was this translation helpful? Give feedback.
All reactions