I haven't paid attention to Netcraft's Web Server Survey, which was once a battlefield between Linux and Microsoft (namely Apache httpd vs Microsoft IIS).
Nginx took the lead from Apache in 2019. However, for the past 3 years Nginx's market share has been on a steady decline, matched by the growth of Cloudflare (10%) and "Other" (25%). Is Amazon AWS lumped with it?
3️⃣ In wenigen Minuten hatte ich dann notfallmässig #Nginx mit Caching davor aufgesetzt und damit flutschte alles. (Bis auf Safari-Requests; die fixte ich dann aber etwas später.)
➡️ Wer sich eine Webseite aufsetzt, sollte die testweise mal mit ein paar Requests bombardieren. Und wenn nötig Caching aufsetzen (was auch #oembed-Requests cacht). Dann ist sie bereit. Sonst nicht.
2/2 @kubikpixel
Der geslashdottete, äh, ge-HN-te Artikel ist übrigens der hier: https://netfuture.ch/2022/05/web3-is-just-expensive-p2p/
I hooked my GNU/Linux-loving son up with an old #lenovo#thinkcenter mini-PC that I picked up at a used AV store for about $50. For another $20, I upgraded the ram to 12GB.
He's got it setup it up with #debian as his first home server, with which he's now hosting a few static websites and an internet radio station for his friends and family. He's got loads of resources to spare for when he gets into running larger services.
You don't need to spend $30+ a month on cloud services when an old recycled office PC will more than suffice.
The best part? Helping him troubleshoot his problems with #DNS and #nginx and all that fun stuff. I've already made every mistake possible over the decades, and he gets to benefit from that. That how it should work!
As a bit of a #homeAssistant project, I noticed my old #RaspberryPi is quite near my 3D printer (basement) and it just runs a #Mosquitto#mqtt server. It has more capacity than that, so I attached an old usb camera, loaded #nginx and wrote some #Python to take a pic of the printer and stuff it into both a web page and a home assistant dashboard.
Fediverse traffic is pretty bursty and sometimes there will be a large backlog of Activities to send to your server, each of which involves a POST. This can hammer your instance and overwhelm the backend’s ability to keep up. Nginx provides a rate-limiting function which can accept POSTs at full speed and proxy them slowly through to your backend at whatever rate you specify.
For example, PieFed has a backend which listens on port 5000. Nginx listens on port 443 for POSTs from outside and sends them through to port 5000:
upstream app_server { server 127.0.0.1:5000 fail_timeout=0;}
This will use up to 100 MB of RAM as a buffer and limit POSTs to 10 per second, per IP address. Adjust as needed. If the sender is using multiple IP addresses the rate limit will not be as effective. Put this directive outside your server {} block.
Then after our first location / {} block, add a second one that is a copy of the first except with one additional line (and change it to apply to location /inbox or whatever the inbox URL is for your instance):
300 is the maximum number of POSTs it will have in the queue. You can use limit_req_dry_run to test the rate limiting without actually doing any limiting – watch the nginx logs for messages while doing a dry run.
It’s been a while since I set this up so please let me know if I mixed anything crucial out or said something misleading.
Always had qualms about #nginx given its developers. Pretty stoked that they have finally forked off. nginx is used far too much in my view. Are there better alternatives?
Hm. I wonder if I can get any fediverse admins onboard to disable all images on their instance on the World Sight Day in October, so that only alt text shows up.
Started a dynatrace trial at work today, so far very promising. Some things are a bit complex, but it's pretty good and in our case priced better than sentry or new relic. #web#dev#php#apache#nginx#fpm
Fastly uses the H2O reverse proxy for fast and secure TLS termination over QUIC, HTTP/3, HTTP/2, and 1.1.
The project site compares its benchmarks only to Nginx. I'd love to see a more recent comparison that includes ATS (Apache Traffic Server), HAProxy, and Varnish/Hitch as fellow reverse proxies for TLS termination.
I have an nginx (1.18/ubuntu) reverse proxy installed on a remote machine, using that to curl several files daily from a remote machine which expects a stable IP.
The nginx process stops accepting connections after ~3 weeks. After restarting nginx everything seems to be fine again. No errors in logs.
I assume something is wrong on the other end, but what can I do except restarting nginx via cron?