2 ms·

Why not just have a main page on a single domain that has links to all the services? That way you only need to remember one domain name.

• Vaslo 2y ago
  You could do that as long as you protected that page from prying eyes.
  • KomoD 2y ago
    Yeah? That would apply to NGINX Proxy too...
• 63stack 2y ago
  Easier to wire up services to each other with domain names, serviceA.domain.tld is obvious, domain.tld:1234 is not
  • Kerbonut 2y ago
    There is also path based, e.g. domain.tld/serviceA, domain.tld/serviceB
    • cess11 2y ago
      Won't work for many services, either they do some websocket stuff or they make assumptions about the URL or whatever. Subdomains are the way to go.
      • Kerbonut 2y ago
        True enough, the app needs to support it.
• aftbit 2y ago
  Another reason to have a domain for each is to get TLS for each service in a standard way.
• TomK32 2y ago
  Of course, a service map comes handy, just another simple way of getting it done. What I meant with the proxy was using e.g. jellyfin.example.com and portainer.example.com instead of the ports. Not to mention that two apps might have the same default port. For those with a multi-machine setup, like running the easy stuff on a 1L machine and having backupservice at multiple locations or the LLMs on a big setup that might even use WakeOnLan the proxy will keep you from having to remember the IPs as well.
• ParetoOptimal 2y ago
  Many use browser history so type a few characters and hit enter rather than navigating to an index page, locating a link, and clicking it.