Skip to content

Comment on Making a Local Web Server Public with Localtunnel

Comments

i understand the case where you don't have a box with e.g. port 80 available and need to use their server as an endpoint, but otherwise is it really that hard to remember ssh -L and -R syntax as the article suggests?

i also don't really see where you'd need to tunnel and serve production traffic from your dev machine versus having a proper staging environment and testing there. that has "bad idea" written all over it.

> we’re all starting to see the benefits of having a production-like environment right there on your laptop so you can iteratively code and debug your app without deploying live, or even needing the Internet.

actually, real professionals have seen these benefits for ages. that is SOP for good programmers.

A lot of great startups were engineered by non-"real professionals", meaning they had little to no formal training in software development and/or little to no experience developing software in a professional setting. A lot of SOP is learned along the way; it is not always so obvious at the outset.

Correct, but I'd also like to point out the self-taught freelancers, small web dev shops, and/or hobbyist hackers that like to build things in a way that's comfortable for them. I wrote that in that way ("we're all starting to see") because it's something I've noticed in the real world (even here in the Valley) that is not necessarily common knowledge yet.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.