this post was submitted on 26 Jul 2024
160 points (94.0% liked)

Selfhosted

40313 readers
230 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I see so many posts and people who run NGINX as their reverse proxy. Why though? There's HAProxy and Apache, with Caddy being a simpler option.

If you're starting from scratch, why did you pick/are you picking NGINX over the others?

you are viewing a single comment's thread
view the rest of the comments
[–] liliumstar@lemmy.dbzer0.com 25 points 3 months ago (1 children)

Good question. I chose it initially because it was open source and way easier (in my eyes) than Apache. I don't recall the others being an option at the time, or I was not aware of them. nginx does what I need without complaint, so I haven't switched.

[–] mystik@lemmy.world 19 points 3 months ago

At $dayjob I switched from Apache to nginx 15+ years ago. It's Callback/Event based process model ran circles around Apache's pre-fork model at the time. It was very carefully developed to be secure, and even early on it had a good track record. Being able to have nginx handle static content without tying up a backend worker process was huge, and let us scale our app pretty well for the investment of time. Since then, Apache implemented threaded + Event based process models, Caddy, traefik, and a bunch of others have entered the scene.

TBH, I think the big thing nowadays is sane defaults, and better configuration, even automatically discovered configuration -- traefik is my current favorite for discovering hosts in consul/Kubernetes/simple host definition files, but since traefik can't directly serve files, I simply proxy from traefik to .... nginx :)