I have a few selfhosted services, but I’m slowly adding more. Currently, they’re all in subdomains like linkding.sekoia.example etc. However, that adds DNS records to fetch and means more setup. Is there some reason I shouldn’t put all my services under a single subdomain with paths (using a reverse proxy), like selfhosted.sekoia.example/linkding?

  • surfrock66@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    ·
    1 year ago

    Subdomain; overall cheaper after a certain point to get a wildcard cert, and if you split your services up without a reverse proxy it’s easier to direct names to different servers.

    • witten@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      Who still pays for certs?? (I say this as non-snarkily as possible.) I just imagined everyone self-hosting uses Let’s Encrypt.

      • surfrock66@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Let’s encrypt is fine for encryption but not identification. I have some stuff which I prefer that on, specifically around demonstrating services that I host at home in the workplace. Having full verification just reduces the questions I have to deal with. It’s like $90/year for a wildcard.

        • witten@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Wow, okay! I guess that’s a different use case than what I’m typically doing.