• paequ2@lemmy.today
    link
    fedilink
    English
    arrow-up
    11
    ·
    4 hours ago

    Actually, one thing I want to do is switch from services being on a subdomain to services being on a path.

    immich.myserver.com -> myserver.com/immich
    jellyfin.myserver.com -> myserver.com/jellyfin
    

    I’m getting tired of having to update DNS records every time I want to add a new service.

    I guess the tricky part will be making sure the services support this kind of routing…

    • suicidaleggroll@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      2 hours ago

      Why are you having to update your DNS records when you add a new service? Just set up a wildcard A record to send *.myserver.com to the reverse proxy and you never have to touch it again. If your DNS doesn’t let you set wildcard A records, then switch to a better DNS.

    • CorvidCawder@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      9
      ·
      3 hours ago

      Wildcard CNAME pointing to your reverse proxy who then figures out where to route the request to? That’s what I’ve been doing - this way there’s no need to ever update DNS at all :)

      I find the path a bit clunky because the apps themselves will oftentimes get confused (especially front-ends). So keeping everything “bare” wrt path, and just on “separate” subdomains is usually my preferred approach.

    • shadowtofu@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 hours ago

      I had the same idea, but the solution I thought about is finding a way to define my DNS records as code, so I can automate the deployment. But the pain is tolerable so far (I have maybe 30 subdomains?), I haven’t done anything yet