When I saw the title I got confused with Node Package Manager lol

I’m the weirdo going with haproxy, but that thing is an absolute beast.

You’ve got those carrots in the wrong direction.

I’m that weird person who just uses nginx and does the config files in a text editor. Been doing it that way since 2010 or so and I’m too used to it to appreciate proxy manager.

It’s interesting how different people have different approaches … I migrate from Caddy to Traefik because I found it magical … Whenever I need to add another selfhosted service I just adapt a docker-compose like this one

version: '3.8'

services:
  homeassistant:
    container_name: homeassistant
    image: ghcr.io/home-assistant/home-assistant:stable
    #image: homeassistant/raspberrypi4-homeassistant:stable
    volumes:
      - ./media/:/media
      - ./config/:/config
      - /etc/localtime:/etc/localtime:ro
    environment:
      - TZ=${TZ}
    restart: unless-stopped
    networks:
      - t2_proxy
      - backend
    labels:
      - traefik.enable=true
      - traefik.docker.network=t2_proxy
      - traefik.http.routers.homeassistant.rule=Host(`home.mydomain.bla.bla`)
      - traefik.http.routers.homeassistant.entrypoints=websecure
      - traefik.http.routers.homeassistant.tls.certresolver=myresolver
      - traefik.http.services.homeassistant.loadbalancer.server.port=8123

networks:
  backend:
    external: true
  t2_proxy:
    external: true

As you can see I just need to change the host and the port in the labels to have a new domain pointing to the right port … I wasn’t able to find an easier way to add a new service to caddy

Man, I started with Apache back in the day which is just nightmarish to manage for simple projects imo, then moved to NGINX, which felt a bit better but still not super intuitive, then NPM, which did make it significantly more user friendly.
Then Caddy came along and swept me off my feet, I still can’t believe it’s as dead simple as it is lol. I tried Traefik for a while because it sounded super interesting and I do love the idea, but it brought a lot of the complexity back with it for admittedly very neat docker integration.
Went right back to Caddy after I moved away from docker as a whole and I couldn’t be happier, I just find it so pleasant to use. Just pure KISS goodness!

So I guess my ranking goes Caddy > Traefik > the rest

I have only used 2 reverse proxies, so I can say with confidence that SWAG > all /s

I’ve been using Traefik, Caddy sounds interesting but I’m definitely not touching my setup until it breaks lmao. Then maybe I’ll give it a shot.

My setup is running NPM and I can’t complain, but I’ll look into caddy as I’ve seen it mentioned a lot.

I saw it mentioned here, I likely won’t change on my setup until something breaks though. 😂

At the first time move to Caddy, I had an issue adding Caddy container to all the current docker networks.
How do you tackle that issue?

Caddy is great, I’ve been using it for all greenfield projects.

P. S. Have you checked out the Caddy API?

Honestly if I had everything in docker I’d use traefic, but I found it horrifically complex to do simple things as soon as you need to branch off of your docker host. I’ve just started using Caddy and it is so user friendly I can’t even believe it.

Traefik configuration is a bit verbose at times, but middlewares are awesome and you can pry them from my cold dead hands