idealwebsolutions / instant-tunnel Goto Github PK

Currently, health of a tunnel is only determined by the source origin. There can be issues that arise with the host that can cause the tunnel to fail even if the origin is still online. This needs to be fixed so both the origin and host (where instant-tunnel is deployed) are monitored.

Redis was a short term solution to get the idea up and running fast, PostgreSQL seems better fit for the job

Add email alerts when a service goes down

Error seems to possibly come from stale database connections being left open...

select * from \"routes\" - read ECONNRESET

Reminder to use a bundler to take advantage of tree shaking...

cloudflared (free) still seems to work, the testing machine running instant-tunnel no longer responds. Needs to be investigated.

Currently you can query for tunnel status using a tunnel id but it would probably be more convenient to emit tunnel specific events from the store.

Argo Tunnel provides us with some basic analytics, maybe some uptime and alerts for when a route crashes

This feature was never implemented and no longer being considered