-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Tunnelmole as an open source alternative to ngrok #1262
Comments
Although I'm not 100% sure how I feel about this right now, I'm not entirely opposed to the idea and I think we could mention other alternatives to ngrok in the documentation. If the implementation is simple enough though, we could add a quick script in A couple of things I noticed:
tunnelmole.com provides commands for installing their service (the following is for Linux machines):
Doesn't seem too intensive though so it's not a make or break for me. Out of the three options you mentioned, I think 1 or 3 would be the most plausible:
Would love to hear from other members on the team to see what they think. |
I get the same error when I try to run I'm fairly certain that we don't want to replace The idea of having it as more of a baked in option is also interesting. I'd love to see a PR for what that would look like. Also, TIL about |
Just published a little wrapper package, |
Just confirmed it's running:
|
I've noticed you have ngrok as the suggested tunnelling solution in your README and also have a script in Procfile.dev.
However, ngrok has a few issues
So, i'd like to update your docs to add tunnelmole. It has the following advantages
Here's the difference in terms of set up and usage
Ngrok
First download and install from ngrok.com
Tunnelmole
Since you guys already seem to have a NodeJS dependency, there is no need to install anything.
Just run
npx tmole 3000
and Tunnelmole will work.There are a few options here
I can also create a script in Procfile.dev, using
npx
to run Tunnelmole without the need to install anything.Let me know your preference and if you'd like me to make a PR with the changes.
The text was updated successfully, but these errors were encountered: