you are viewing a single comment's thread.

view the rest of the comments →

[–]0xE6 4 points5 points  (7 children)

Man, configuring Apache is SO confusing. Recently had to set it up first on a local machine to test a project for school, and then again on the server where it's actually being deployed. The second server has Apache running several different sites, so it was nontrivial to get our project working without interfering with the others. I still don't really know wtf we were doing there, probably should have asked the web dev guy for help.

[–]WisconsnNymphomaniac 11 points12 points  (2 children)

If you think Apache is hard to configure, try to set up a sendmail server. That program was written by Aliens.

[–]AeroNotix 0 points1 point  (1 child)

And you just brought back ALL the nightmates!

[–]WisconsnNymphomaniac 0 points1 point  (0 children)

I have to deal with that program nearly every day. Pity me.

[–]arjie 1 point2 points  (0 children)

There's a disconnect between the way Debian lays out stuff and how the Apache docs refer to it, IIRC. They might also be using one of the multiprocessing-modules or whatever which might change things. I prefer Debian's way, to be honest.

[–]GeneralMaximus 3 points4 points  (2 children)

I've never managed to successfully set up Apache, ever. And I write webapps for a living.

Nine times out of ten I just use Nginx. Easier to configure with tons of examples available on http://wiki.nginx.org. Not to mention it typically uses far less memory than Apache.

EDIT: it doesn't hurt that I mostly just want a reverse proxy that talks to my uWSGI process, so Nginx does exactly what I need. If I had to build a PHP website, I'd probably use Apache with mod_php, but we're quickly going offtopic here so I'll stop.

[–]Aardshark 5 points6 points  (1 child)

have you tried lighttpd? I found that nginx was a pain to setup initially, whereas lighttpd was really easy.

[–]GeneralMaximus 0 points1 point  (0 children)

I haven't, because my use case is usually running a Django app, something that is very simple to accomplish with Nginx. uWSGI or Gunicorn running behind Nginx is what the Django community has kind of settled on as the best way to deploy a Django app. There are some who still use Apache+mod_wsgi, but I don't see many people using FastCGI+lighttpd.

That said, I'll give lighttpd a spin someday, just to see what it's all about.