Serveo: Expose Local Servers to the Internet

#1

Post by ducaale » Sat, Jun 22, 2019, 7:34 PM UTC

Serveo: Expose Local Servers to the Internet
serveo.net

Re: Serveo: Expose Local Servers to the Internet

#2

Post by dang » Sun, Jun 23, 2019, 12:14 AM UTC

A thread from 2017: https://news.ycombinator.com/item?id=14842951

Re: Serveo: Expose Local Servers to the Internet

#3

Post by FloatArtifact » Sun, Jun 23, 2019, 3:56 AM UTC

Never really figured out how to use it with for Minecraft server for over predictive firewalls.

Re: Serveo: Expose Local Servers to the Internet

#4

Post by Advaith » Sun, Jun 23, 2019, 4:04 AM UTC

I've been using ngrok for development purposes. This seems like an interesting alternative.

Re: Serveo: Expose Local Servers to the Internet

#5

Post by tourdownunder » Sun, Jun 23, 2019, 4:22 AM UTC

I've wanted to do something similar to test webhooks in the past.

Re: Serveo: Expose Local Servers to the Internet

#6

Post by neilk » Sun, Jun 23, 2019, 4:50 AM UTC

I really like Serveo.

I’ve used it to develop proper previews and unfurls for social media. Facebook etc need a real public URL to even show you a preview.

And the other day I used it as a quick way to debug a server-client communication issue. I’m developing a server, and the client developer is in a completely different location. For a while I kept deploying dev servers with little tweaks, but our progress was slow, Then I gave up and just exposed a local running server to the internet via Serveo. My counterpart pointed his client there, and we quickly iterated to a solution.

Yes we could have solved this in many other ways (remote debugging, VPNs, etc) but this was surprisingly easy.

Re: Serveo: Expose Local Servers to the Internet

#7

Post by vajra » Sun, Jun 23, 2019, 4:55 AM UTC

This is nice and i remember seeing this a while ago. However we couldn’t use it since during local development, the engineers are quite relaxed with secret keys, passwords, standard protocols …etc.

Re: Serveo: Expose Local Servers to the Internet

#8

Post by rohan1024 » Sun, Jun 23, 2019, 5:16 AM UTC

NAT has crippled the Internet. We are permanently dependent on public facing servers to route packets from one device to the other.

This service is absolutely not needed in a non-NAT world. And I strongly believe we have lost a lot by being completely dependent on client-server model of Internet.

I've written more about it here

https://www.ankshilp.in/post/the_broken_promise_of_internet/

Re: Serveo: Expose Local Servers to the Internet

#9

Post by tambre » Sun, Jun 23, 2019, 5:31 AM UTC

rohan1024 wrote: post #8

NAT has crippled the Internet. We are permanently dependent on public facing servers to route packets from one device to the other. This service is absolutely not needed in a non-NAT world. And I strongly believe we have lost a lot by being completely dependent on client-server model of Internet. I've written more about it here https://www.ankshilp.in/post/the_broken_promise_of_internet/

Fortunately we're being uncrippled again by the continued deployment of IPv6 [0].

[0]: https://www.google.com/intl/en/ipv6/statistics.html

Re: Serveo: Expose Local Servers to the Internet

#10

Post by travbrack » Sun, Jun 23, 2019, 5:35 AM UTC

rohan1024 wrote: post #8

NAT has crippled the Internet. We are permanently dependent on public facing servers to route packets from one device to the other. This service is absolutely not needed in a non-NAT world. And I strongly believe we have lost a lot by being completely dependent on client-server model of Internet. I've written more about it here https://www.ankshilp.in/post/the_broken_promise_of_internet/

Buckle up because it'll be a while before ipv6 gets mass adoption and folks will need to support v4 long after that.