← Back to Forum
2
Setup & Configuration
LocaltoNet setup for multiple local services, one tunnel each or reverse proxy?
I've got a couple things I want reachable from outside, probably a game server, a small web app, and maybe an admin page, and I'm trying to set this up in a way that won't be annoying to maintain later. Not sure if people usually do one LocaltoNet tunnel per service, put the HTTP stuff behind one local reverse proxy, or keep everything separate and locked down as much as possible.
Mainly looking for the practical side, like how you name stuff, handle ports/local DNS, and what you avoid exposing from the start so future changes don't turn into a mess.
Comments (3)
Put only HTTP stuff behind one local reverse proxy, and give anything non-HTTP like Minecraft its own tunnel, mixing those usually turns into annoying port/accounting junk later. I also keep admin pages off the public side entirely unless I absolutely need them, then I expose them on a separate temporary tunnel so I can kill it without touching the app routes.
Name tunnels after the service and env, not the port, stuff like mc-prod, app-dev, admin-temp saved me a lot once ports changed and I was scared to rename things later. I keep the real port mapping in compose or a little notes file, but the public-facing name stays tied to what it is, not how it happens to be wired today.
Yeah, naming by service plus env is probably the bit I was missing, I was definitely about to bake port numbers into everything and regret it later. I’ve got most of this in Docker anyway, so keeping the actual port mapping in compose and letting the tunnel name stay stable makes sense, do you also do the same for local DNS hostnames or keep those a little shorter?
Please log in to post a comment.