Comment

Comment on After 1.5 years of learning selfhosting, this is where I'm at

<- View Parent

xantoxis@lemmy.world ⁨9⁩ ⁨months⁩ ago

I can answer this one, but mainly only in reference to the other popular solutions:

nginx. Solid, reliable, uncomplicated, but. Reverse proxy semantics have a weird dependency on manually setting up a dns resolver (why??) and you have to restart the instance if your upstream gets replaced.
traefik. I am literally a cloud software engineer, I’ve been doing Linux networking since 1994 and I’ve made 3 separate attempts to configure traefik to work according to its promises. It has never worked correctly. Traefik’s main selling point to me is its automatic docker proxying via labels, but this doesn’t even help you if you also have multiple VMs. Basically a non-starter due to poor docs and complexity.
caddy. Solid, reliable, uncomplicated. It will do acme cert provisioning out of the box for you if you want (I don’t use that feature because I have a wildcard cert, but it seems nice). Also doesn’t suffer from the problems I’ve listed above.

source

Sort:hotnew top

oh_gosh_its_osh@lemmy.ml ⁨9⁩ ⁨months⁩ ago
Fully agree to this summary. traefik also gave me a hard time initially, but once you have the quirks worked out, it works as promised.

Caddy is absolutely on my list as an alternative, but the lack of docker label support is currently the main roadblocker for me.

source
- 7Sea_Sailor@lemmy.dbzer0.com ⁨9⁩ ⁨months⁩ ago
  May I present to you: Caddy but for docker and with labels so kind of like traefik but the labels are shorter 👏 github.com/lucaslorentz/caddy-docker-proxy
  
  source
  - oh_gosh_its_osh@lemmy.ml ⁨9⁩ ⁨months⁩ ago
    Nice catch and thanks for sharing. Will definitely check it out.
    
    source
- 0xZogG@hachyderm.io ⁨9⁩ ⁨months⁩ ago
  @oh_gosh_its_osh @xantoxis for #k8s solution though I think traefik has advantage of providing configuration via CRDs, no?
  source
jkrtn@lemmy.ml ⁨9⁩ ⁨months⁩ ago
I feel so relieved reading that about traefik. I briefly set that up as a k8s ingress controller for educational purposes. It’s unnecessarily confusing, brittle, and the documentation didn’t help. If it’s a pain for people in the industry that makes me feel better. My next attempt at trying out k8s I’ll give Kong a shot.

I really like solid, reliable, and uncomplicated. The fun part is running the containers and VMs, not spending hours on a config to make them accessible.

source
- notfromhere@lemmy.ml ⁨9⁩ ⁨months⁩ ago
  I have traefik running on my kubernetes cluster as an ingress controller and it works well enough for me after finagling it a bit. Fully automated through ansible and templated manifests.
  
  source
  - xantoxis@lemmy.world ⁨9⁩ ⁨months⁩ ago
    Heh. I am, as I said, a cloud sw eng, which is why I would never touch any solution that mentioned ansible, outside of the work I am required to do professionally. Too many scars. It’s like owning a pet raccoon, you can maybe get it to do clever things if you give it enough treats, but it will eventually kill your dog.
    
    source
    notfromhere@lemmy.ml ⁨9⁩ ⁨months⁩ ago
    Care to share some war stories? I have it set up where I can completely destroy and rebuild my bare metal k3s cluster. If I start with configured hosts, it takes about 10 minutes to install k3s and get all my services back up.
    
    source
    -> View More Comments