3 ms·
Here’s an empirical example. I followed a step by step tutorial on how to setup a server with Apache + Linux + SSL. The backbone of the internet. It’s still n
by kbrannigan 4y ago
Here’s an empirical example.
I followed a step by step tutorial on how to setup a server with Apache + Linux + SSL.
The backbone of the internet.
It’s still not working , and it’s been two days.
Software is cobbled together with ducktape and cowchips.
After 10 years in the field. My take is:
We’ve lied to ourselves so much that we believe our own lies
- ComputerGuru 4y agoCounterpoint: follow a different guide, use nginx or caddy instead of Apache, and you can be live in under thirty minutes. In all cases, this has nothing to do with t to he question. It wasn’t about how smart you have to be to set it up yourself, it was about how robust or fragile it is once put into place. A better point would be that we had certificates with ten-year expiration (not fragile) but susceptible to a myriad of advanced security issues. The solution was to reduce that to certificates that expire every few months, held together by daemons and scripts that renew them automatically in the background, significantly increasing the number of simultaneously moving parts and making the whole more fragile (with obvious security benefits).
- kbrannigan 4y agoI can agree with that. Right now going live is all that matters. To add to your point: I chose the most popular stack with the biggest mindshare, just in case something goes wrong, I’m a one man shop, but why fight against it. I’ll try Ngnix…
- kbrannigan 4y agoIt is my belief that engineers get bored and the create the most convoluted solution for the simplest problems. More complex = more smartsss. I want to move away from model T, I want a F150 with push to start
- pixl97 4y agoEh, I wouldn't use the model T as a good example. A hand crank that could kill you, and the acceleration and gear system were a gigantic mess compared to the cars that showed up a decade or two later. There are plenty of later model cars that add back seemingly unneeded complexity for little gain that would be better examples.
- elitepleb 4y agoApache isn't known to be the most user friendly, instead consider caddy[0], where a full featured web proxy/fileserver can be as easy as: example.com { reverse_proxy localhost:9000 } [0] https://caddyserver.com/docs/getting-started https://caddyserver.com/docs/getting-started
- pixl97 4y agoApache is from the days where everything in computing was difficult and a massive number of lessons about complexity and security had not been learned yet. It really only exists because it was the only option at some point in the past and software grew up around it so it kept momentum. If you're doing anything new you wouldn't use it at all, and instead use one of the multitude of servers that are far simpler and better at the same tasks.