Tech
Routeup – stable local HTTPS URLs and opt-in public tunnels
I built Routeup around a simple idea: local apps should use their real names.
It was inspired by Portless , but I also wanted built-in public tunneling, selective path exposure, request inspection, and live logs.
Instead of opening localhost:3000 , I can give a project a stable, trusted HTTPS URL and keep using it across restarts:
https://example-app.localhost
The app stays local by default. When an external service needs access, I can expose the whole route or only selected paths s...
Read the full discussion on Lobsters
This article was aggregated from Lobsters. Click to join the conversation.
View on Lobsters