3 ms·
Good advice but still not entirely necessary The issue here seems to be a less than optimal Apache configuration I couldn't agree with you more. The problem i
by mootothemax 16y ago
Good advice but still not entirely necessary
The issue here seems to be a less than optimal Apache configuration
I couldn't agree with you more. The problem is my Apache knowledge pretty much well starts and ends with setting up virtual hosts. A year ago I was having serious issues with my Apache set up, and spent hours trying to reduce its memory footprint, and playing with lots of other settings, all to no avail. So I gave up, installed nginx... and it just worked. Which is why I'm so evangelical about it :)
That said, I'm certainly not against Apache; just the setup time and my abject failure. Which is, most likely, incompetence ;)
- petercooper 16y agoYeah, Apache is like a giant lump of clay you need to "sculpt" into something useful, whereas nginx is a fast and empty potter's wheel waiting for you to throw the clay on ;-) nginx is definitely well worth it if you don't have complex Apache-specific requirements. Another alternative I've been playing with lately is running haproxy on port 80 and then throwing requests to different daemons (like Apache and nginx) based on the host header.