supersu on Nostr: I think you are a little confused here, apps do not need to integrate holesail to use ...
I think you are a little confused here, apps do not need to integrate holesail to use it.
Holesail in itself is a proxy, it kind of binds two ports between different devices, so apps just need to use localhost:port as the url.
When I say "integrating holesail", I mean including holesail in the app itself so that users don't have to do the installation and running.
For example, for an apache server running on port 80, I can wrap holesail around it with holesail --live 80 --host localhost
Then on another device: holesail <connection string> --port 3434 --host localhost, now any app on my second device that needs the data from server1, will use the URL http://localhost:3434/
There is no need for manual integration, but for the sake of simplicity and accessibility, it is better to do so.
The above is a manual approach, now if I bundled holesail with apache2 and made it print out a connection key for ever vHOST by default, that would be holesail integration.
Holesail in itself is a proxy, it kind of binds two ports between different devices, so apps just need to use localhost:port as the url.
When I say "integrating holesail", I mean including holesail in the app itself so that users don't have to do the installation and running.
For example, for an apache server running on port 80, I can wrap holesail around it with holesail --live 80 --host localhost
Then on another device: holesail <connection string> --port 3434 --host localhost, now any app on my second device that needs the data from server1, will use the URL http://localhost:3434/
There is no need for manual integration, but for the sake of simplicity and accessibility, it is better to do so.
The above is a manual approach, now if I bundled holesail with apache2 and made it print out a connection key for ever vHOST by default, that would be holesail integration.