Linux/devops/web question. Are there open alternatives to cloudflare's "tunnel thingy"?
Say that I want to host my website https://samuels.bitar.se on a raspberry pi at home but I don't want to expose my home ip, how would I solve this? I know I can do it with Cloudflare but I don't want to use Cloudflare. Can I setup like an nginx proxy on a VPS and do like an ssh tunnel or something? Or are there other solutions?
I learned abour zrok but I don't know if that will work.
@samuel if your content is (partly, semi) static, using a caching reverse proxy can help reduce bandwidth used on your origin uplink and improve "speed" (reduce latencies, increase bandwidth) for your users. some options are #apachetrafficserver#freenginx and #varnishcache, only to name a few. my recommendation should be obvious, but you have the choice and a lot of options.
as a pure (non caching) forwarding tcp or http proxy #haproxy is a good choice.
dem vielen Wasser, das hier überall auf Wiesen und Feldern steht
meiner Affinität zu Keyboards als primäres Interaktionselement mit Computern …
… und welchen Keyboard-Shortcut ich in Firefox schmerzlich vermisse
der macOS App Rectangle
dem Fork von nginx zu freenginx und wie ich am Wochenende nach 19 Jahren ausschließlich nginx-Nutzung mit Caddy erstmals einen anderen Webserver angeschaut habe und seit dem ziemlich begeistert bin
einer Anleitung wie man gute technische Dokumentation schreibt
mkcert und wie es xca als Management-Tool für meine lokale CA abgelöst hat
I am still unsure of what the #freenginx thing actually implies. Obviously everyone wants to side with the plucky dev against the faceless corp, but I also noticed this:
Dounin complains, if I'm reading this correctly, that #NGINX corp sent a #security advisory about an important bug rather than just wait for a regular release on the regular schedule. The bug was in an experimental part of the web server (namely HTTP3 support) so the solution presumably for end users was to disable that feature on production, which was strictly optional in the real world, it wasn't that the only way to fix it was updated code.
And... I'm not seeing what's wrong with that. Obviously I don't want disclosure of the "Suddenly everyone has to wait for an update because now all the script kiddies know" variety, but otherwise early disclosure is good, correct?
Genuine question, would be curious to know your thoughts.
Le fork de nginx, on a des infos sur d'autres développeurs qui auraient rejoint le projet ?
Parce que si le mec est tout seul, finalement j'ai l'impression que c'est beaucoup bruit pour pas grand chose..