Expose – A fully open-source ngrok alternative written in PHP
github.com
github.com
Also, not sure why so many people seem to take "... written in PHP" as a gauntlet slap to their own face, instead of some additional technical information.
If you have nothing to add to the conversation other than witty snark about PHP, maybe your time would be better spent writing a competing open source product in a language of your choice, giving it away for free, and then letting users compare their pros and cons?
Seeing this thread derail into a discussion about PHP is pretty annoying. It seems to happen to anything PHP-related here. Do that all day long please, if someone comes here saying PHP is the best language... but he created something useful and open sourced it - that deserves more than toxic bike shedding about your favorite toys.
It can be handled using a single go binary using pgrok which comes less the source code size and not to mention without any dependencies on almost all platforms!
This requires unnecessary things to bundle and too complex for some simple stuff. Mileage may vary though.
But just my views.
https://github.com/jerson/pgrok
...which does look useful indeed.
I don't even know how to run a Go server.
These tunneling services use a client-server architecture with the server-side running on a public IP address. A static binary written in Go, like pgrok, is ideal for the client-side. On the server-side, you want an app server that is both common and can dynamically load a module. A dedicated Go server makes sense if you are building a service but not if you want to add functionality to an existing app server with a public domain name.
[1] https://pociot.dev/28-introducing-expose-an-easy-to-use-tunn...
The reason for asking is I'd like to find a self-hosted ngrok solution for development.
Going to try Expose soon, really excited by what it brings to the world of PHP without having to support a new stack.
Zapier is built on Python, Django, React, Node.js, and AWS
Were you aware of the tradeoffs you made with that stack. Zapier has many technical issues: https://ca.trustpilot.com/review/zapier.com
If you went with a different stack I don't think you would have half of the issues your customers are reporting.