[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Search] [Home]
Board
Settings Home
/g/ - Technology


Thread archived.
You cannot reply anymore.



File: 7.png (76 KB, 852x446)
76 KB
76 KB PNG
You fags would argue about anything
>>
>>70171910
This house is of the opinion that OP is a faggot
>>
OpenBSD httpd
>>
>>70172083
Based and red pilled.
>>
>>70172083
based!
>>
>>70171910

in some instances espicially with PHP you would use both.

> But don't its retarded
>>
>>70172722
Imagine using Apache as an application sever when uwsgi exists.
>>
>>70171910
Monothread server in express js is the only acceptable answer
>>
Caddy
>>
Apache is good but Nginx is god tier.

Just be thankful we have 2 (two!) incredibly good web servers available.
>>
>>70171910
Apache because it's the one I chose at random and I don't feel like learning another one
>>
>>70171910
Apache is slow as shit and the attack surface area on it is huge. Nginx is very nice, but all the real high power features are locked behind a subscription that costs two kidneys and a firstborn. Still, the free version is the best webserver in common use.
But lots of languages self-host quite well now, and nginx ends up just doing reverse proxy work. If you're just doing that, then there are more tailored alternatives.

HAProxy is fantastic for reverse proxy and load balancing work. It's used everywhere for good reason.
Traefik is the new hotness for Kubernetes users. It's nice, but if you're not doing the whole containermeme then HAProxy is better.
>>
Lighttpd
>>
nginx because im not a retard
>>
> Not using bash and nc as your webserver
>>
If you strip down Apache httpd far enough, use event MPM and have AllowOverride None, the performance difference isn't all that big. Most processing time goes into the dynamic pages, which should be handled using e.g. FastCGI workers anyway. Static files use pretty much the same system calls.
I'm a big fan of nginx because of the config files, but they were bought by F5 this week. I really hope they don't fuck up, otherwise it's back to Apache httpd.
>>
File: fb_computer_science.jpg (610 KB, 2592x1936)
610 KB
610 KB JPG
>>70171910
Nginx is obviously the correct choice. The only reason to use Apache is if you need a ton of autistic plugins.
>>
>>70175429
based

ganoo/lunix is a joke anyway, your web server might as well be
>>
>>70171910
Nginx because configs aren’t xml. Only real use case for Apache where there is a tangible benefit is a single PHP instance. If you have multiple upstreams, nginx steamrolls it.
>>
>>70171910
There's no question about it, Nginx has more features, updated more often and is lightweight. Although its license and distribution are questionable.
>>
[kode]python -m http.server[/kode]



Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.