2 publicaciones etiquetados con "ssh"

You're building a Stripe webhook handler. Your local dev server is running on port 3000. Stripe needs a public URL to send events to. You do what every developer has done before: open a terminal and type ngrok http 3000.

It works. For a while.

Then you hit the rate limit. Or the random subdomain changes every restart. Or you need to whitelist a specific IP and ngrok's plan doesn't cover it. Or your company's security policy blocks third-party tunneling software.

At Filess, we built our own managed tunnel infrastructure, and we're making it available as part of the platform. Here's the full technical breakdown of how it works.

You're debugging a critical bug in the Example App. You need to see the raw data in the sale table to understand why the totals aren't adding up.

You fire up TablePlus or DBeaver, but you hit a wall. The database is (rightfully) in a private network.

How do you get in?

Do you temporarily open port 3306 to the world? Dangerous. Do you deploy a VPN server just for this? Expensive.

The answer is an SSH Tunnel.