Traefik-v2-examples VS NGINX Unit

Theres also traefik guide but the contrast in complexity is apparent right away.

Traefik that I tried first is very powerful but there are few abstraction layers and bit of complexity that I felt like I had to re-learn it every time I was about to do a change. But it is very powerful in dynamic enviroments where one spins often enough more new containers.

My first reverse proxy was traefik, but it was just too complex, with too many abstraction layers for my use. I needed to re-learn it every time I went to make changes.

I tried traefik. As I was learning it, which was like a week or two of effort, I actually wrote a guide that somehow got 500 stars on github...

Theres also traefik, that people recommend, but IMO for home stuff it is too complex with too many abstractions. Caddy is literally just giving it port 80 and 443 and a single clean config file.

Traefik is actuall business aimed and powerful and probably worth learning if you would need to manage lot of containers and change stuff dynamically on the fly. But it is just so damn complicated and you kinda need to re-learn it every time you return to it. Here is guide for that one..

You can try look here

Here is a decent guide that gets you going.

Have you considered going caddy instead of traefik?

How to reverse proxy with traefik

Nginx Unit application server.

This is great to read! Thanks for all the great input!

I check the comments next week and make sure to address the issues / ideas mentioned. If you don’t mind feel free to drop a comment here as well with your ideas / needs. https://github.com/nginx/unit/issues/945

I will work on a compression between Nginx and Unit to close this gap in our documentation.

You could try running h5ai with NGINX UNIT.

nginx, but nginx-unit looks very interesting. I might switch a few docker containers to use it before trying to use it natively.

unix:/filesocketheadache (problems) verses unix:@abstractsocketmagic (problem solved)

Try Nginx Unit to get away from the php-fpm complexity. It runs on http by default so it's super easy to spin up and access by itself (no need for an extra http server) or behind another http gateway as a simple proxy.