Closed despiegk closed 1 year ago
Can we have more elaboration on the requirements?
sftpgo
functionalities should be exposed via the client?sftpgo
server itself in the proxy as well?cc @xmonader
I believe @despiegk meant to be able to launch server as a subcommand of the proxy or the functionality to be exposed as a module on the proxy
the code needs to be in the golang binary, so we only have one
There is no way to integrate the server into web3 due to the fact that the server logic in sftpgo
not being exposed. The alternative is to integrate the code ourselves but this will mean extra overhead for development and maintenance in the future in case we want to have the latest upstream updates
Integration mostly done, just needs to consider how to deliver the necessary static failed needed by sftpgo to the web proxy deployment
please define what we will have now?
Sftpgo can be run using web3 proxy by following this doc: https://github.com/threefoldtech/web3_proxy/blob/development_sftpgo/manual/src/server/sftpgo.md
Verified.
I was able to follow the docs and run sftp go through the webproxy using both methods mentioned in https://github.com/threefoldtech/web3_proxy/blob/development/manual/src/server/sftpgo.md
First method is by running docker compose (recommended method ) This method is very easy and simple all you have to do is run one command in the root directory of the webproxy and you're good to go.
Second method is by manually configuring the instance through sftpgo.json
file and the required env vars.
This method is a bit more complicated and has more steps, but the flow is documented well.
and it works fine with both methods and all the defined functionalities are working without any issues.
see if we can compile and load it in web3 proxy
maybe an option defines if we load it or not and what the admin username is