You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use asyncpg through a socks 5 proxy. I need this because the postgresql instances are running inside a docker overlay network (swarm). The IP addresses of the servers are not fixed, and it is not possible to access them directly.
If I had a single postgres server, then it would not be a problem to manually create a tunnel. But I need to connect to several different servers, and their ip addresses are changing. Manually creating a bunch of host aliases and creating multiple tunnels is just not practical.
Would it be possible to add a layer that would allow me to add my own callback for creating the TCP socket for a given host name + port pair?
The text was updated successfully, but these errors were encountered:
If you only want a callback functionality and going to implement the proxy handling code yourself, as opposed to having asyngpg natively support socks5, this is similar to #1054
I would like to use asyncpg through a socks 5 proxy. I need this because the postgresql instances are running inside a docker overlay network (swarm). The IP addresses of the servers are not fixed, and it is not possible to access them directly.
If I had a single postgres server, then it would not be a problem to manually create a tunnel. But I need to connect to several different servers, and their ip addresses are changing. Manually creating a bunch of host aliases and creating multiple tunnels is just not practical.
Would it be possible to add a layer that would allow me to add my own callback for creating the TCP socket for a given host name + port pair?
The text was updated successfully, but these errors were encountered: