It seems that basic web sites made by uploading html and other files are going extinct, in favor of web apps like CMSs and blogs. As a result, the majority of the functionality provided by web servers like Apache is becoming unnecessary.
As an example, any web app which interfaces with Apache via Rack [rubyforge.org]middleware needs only the enabling of mod_rack. Other than that, you don't need to touch apache2.conf. Apache basically just handles the sockets; the rest of its functionality goes unused.
Third party mods are not part of Apache proper. The other stuff really should be done by the app, where it can be altered without HUPing any processes.
"Laugh while you can, monkey-boy."
-- Dr. Emilio Lizardo
web servers to app servers (Score:4, Interesting)
It seems that basic web sites made by uploading html and other files are going extinct, in favor of web apps like CMSs and blogs. As a result, the majority of the functionality provided by web servers like Apache is becoming unnecessary.
As an example, any web app which interfaces with Apache via Rack [rubyforge.org]middleware needs only the enabling of mod_rack. Other than that, you don't need to touch apache2.conf. Apache basically just handles the sockets; the rest of its functionality goes unused.
Re:web servers to app servers (Score:1, Insightful)
Yea who cares about:
- redirects
- URL remapping
- mod_php
- mod_perl
- mod_svn
- web dav
- https
Re: (Score:2)
Third party mods are not part of Apache proper. The other stuff really should be done by the app, where it can be altered without HUPing any processes.