logoalt Hacker News

flosslytoday at 10:04 AM2 repliesview on HN

we need a way to access locally running web apps without doing an ugly http://localhost:8022 and having to remember that.

I'd say http://localapps should give an overview of all web apps running locally, with links to them. Those links should follow a naming scheme where the hostname ends with `.local` or smth.

So: http://claudecode.local


Replies

mr_olivetoday at 11:00 AM

Hah, I was dealing with this problem today.

My approach: Add entries for my localhost apps to `/etc/hosts`, and set up nginx as a reverse proxy.

Now when I go to `http://myapp.local` in the browser, `/etc/hosts` tells it to go to `localhost:80`. The http server sitting there knows which port to send the request to. I also made a systemd service that starts nginx automatically.

Now I have meaningful URLs for local apps, and I don't have to remember which one is listening on which port.

fc417fc802today at 10:32 AM

Won't that be cluttered by various random processes listening via 0/0? Perhaps we need a standardized service that web apps can register with.