reverse proxy

[despiegk]

• see how to extend with reverse proxy basic functionality
• e/g/ https://3botip/dao goes to http://localhost:8888
• the localhost would be our V backend
• sftpgo uses letsencrypt already, so https to http should be easy
• the 3botip is the pub ip address using letsencrypt
• see if we can add API for this so we can configure it from VLANG

[despiegk]

this allows sftpo to be the default front end for all our functionality

[xmonader]

even with a public ip, you need the domain to be resolvable by let's encrypt, otherwise it won't be able to do dns01 or http01 to verify the ownership of a domain to issue a certificate

[despiegk]

is not a prob, pub ip addr ok for now

[alichaddad]

I am not entirely sure what is needed here. Is the goal to make use of sftpgo server to expose the web3 proxy API? What is the API that we can add and to configure what?

[alichaddad]

I am going to add a new endpoint in sftpgo: /dao that routes to a configurable server as a start until more details are gathered

[despiegk]

we are ok, we can cancel this one, we can work around it using our web2gateway, ok to close