That's a fair thing to do if you're building a frontend application. Though this posts example is purely just to show off something running from localhost. I've used ngrok in the past to test webhook implementations sent from third parties. For example, I needed to capture a webhook fired from DocuSign and debug it (in dotnet) but DocuSign doesn't know anything about my localhost. Deploying to a server doesn't help either because then I can't step through my code! Scenarios like this is where things like ngrok really shine. But if you're just wanting to show off work, agreed may as well just deploy somewhere and have a bit more guarantee it'll always be accessible.
To be honest this seems like a hassle. For this use case I would just put it on Netlify tbh. If you use the CLI that's just on command.
~Cheers
That's a fair thing to do if you're building a frontend application. Though this posts example is purely just to show off something running from localhost. I've used ngrok in the past to test webhook implementations sent from third parties. For example, I needed to capture a webhook fired from DocuSign and debug it (in dotnet) but DocuSign doesn't know anything about my localhost. Deploying to a server doesn't help either because then I can't step through my code! Scenarios like this is where things like ngrok really shine. But if you're just wanting to show off work, agreed may as well just deploy somewhere and have a bit more guarantee it'll always be accessible.
But using localhost.run doesn't seems to be hassle. Its just one command?
Agreed its nice to have those kind of options however I would likely use Netlify or Vercel.