I’ve been running 2 linodes for a number of years now - one has my website (wordpress) on it and one has a Foundry VTT server running. Both are separate linodes, and I use Google Domains to point [site.tld] to the wordpress VPS and foundry.[site.tld] to the other linode.

For a few services I run at home within my own network (Sonarr, Lidarr, Plex, etc.) I’ve started to use Docker and Portainer, and I like how easy it is to set things up (and remove them if they don’t work). I’d like to redo my VPS similarly - I’d like to have a single linode, as a Docker host, and have the main domain point to a Wordpress container, a subdomain point to a Foundry container, and be able to easily add other containers for something like freshrss, etc. My goal is to be able to quickly spin up a docker via a compose file (portainer would be preferred), have it automatically reach out to letsencrypt to get a cert for the relevant subdomain, and have that subdomain point to that docker container.

I’ve been doing some searching around, and there seem to be a number of options, things like nginx reverse proxy, traefik, etc. and there are a lot of conflicting results.

Does anyone here have an opinion on this or some advice as to what the best option to look into might be?

    • smegger
      link
      fedilink
      11 year ago

      I’ve found npm to be fairly easy to setup. But I’m not far from your situation, trying out various options to see what works best for me

      • hispeedzintarwebzOP
        link
        fedilink
        11 year ago

        That’s pretty much where I am. This isn’t my day job, it’s something I mess with for fun and so I’d like to make it easy not just to set up but to expand if necessary, and easy enough that if I don’t touch it for a year and come back to it I won’t be completely clueless!

    • Scott
      link
      fedilink
      11 year ago

      Here’s a 3rd to convince you even more, I have it running on several instances.

        • beto
          link
          fedilink
          11 year ago

          If you don’t have any special needs, NPM is a good way to go. Even if you do, some flexibility is available in UI advanced options and directly modifying the config if you have the nginx knowledge (although I’d advocate not to do it, if possible).

          There’s a docker-compose file for it, so it should adjust to your setup too.

        • @[email protected]
          link
          fedilink
          11 year ago

          I also use NPM, which can be quite buggy sometimes (including completely breaking the database). If it works, itsit’s quite nice. I’ve proxied 30 servers with it