Skip to main content

ngrok in production and other uses

I recently came across ngrok and while the demo that I watched was recommending it development environment I think it might have a few more use cases.

The example that was given: You have implemented some application or feature that you want to share but the user is remote, outside the firewall, or asking the user to update his hosts file make the process painful.

Enter ngrok.

Register with ngrok. Then download their client application. Launch your application in localhost mode. Then configure and launch the ngrok client. The ngrok client will open a long poll connection to the ngrok server. You give the user a target URL to enter into his browser... and voila.

The user's browser connects to the ngrok server, which forwards the message request to the ngrok client, which then opens a connection to the configured client application. The experience is complete.

What makes this model desirable is several fold [a] all applications would be configured as localhost support the just-one executable model [b] (a) supports a similar docker model [c] some firewall routers need to restart or [d] router risk associated with firewall rules [e] this is an inside out connection rather than an outside in.

It's very obvious how this works in development. It's just a way to share.

In CI, continuous integration, this solution would promote a dynamic network structure that would require minimal care and feeding. With a touch of good luck would not require massive DNS changes.

** I have no idea what the capacity requirements are and whether it's fast enough for production but it's exciting as part of a complete solution.

** ngrok has logging and replay features which would need to be disabled in production. Additionally there is no mention of SSL. I presume that ngrok would act as a man in the middle so it would be better inside your firewall.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…