I don't chime in too often, but I spend a lot of time in #php #mysql #javascript, etc on a few different IRC networks. I won't say 'often', but I frequently hear mention of other web servers. The people that know what they're talking about tend to shut them up and explain why Apache is super-duper, but I do agree that sometimes apache can be daunting. Since I mainly use Apache for a LAMP purpose, I've gotten accustomed to using packages like xampp that do everything for you.
Problems with these packages is they do so many things without you knowing, and you often are using too many modules than you need. I don't consider this "bloatware" ala MS, as I don't see performance slowing, but I'm also running Apache on some beasty servers. Here's a stupid question: What are the available front-ends for configuring Apache? I've used webmin, ispconfig, etc but it's fugly and it not focused solely on Apache. I wonder if there could be two different types of web-based configurators for apache: (One) would be an online-survey on the Apache website where people are asked what they want to do with apache, or what modules they need. Then the binary download is prepared just for them (as these people that don't know too much are definitely not going to be building this thing themselves) (Two) would be some web-interface running on their localhost on a non-standard port that allows people complete control over the server. I can't seem to find google, so I'll assume there's always many things like this out there, but if they are... I don't know about them when I look to download apache, so they either must not be marketted well, or must suck. I'm thinking of an interface like PFSense ( http://www.pfsense.org/ ) has. Where does tomcat fit into this mix? On Dec 13, 2007 6:56 AM, Joshua Slive <[EMAIL PROTECTED]> wrote: > On Dec 13, 2007 5:57 AM, Nick Kew <[EMAIL PROTECTED]> wrote: > > On Thu, 13 Dec 2007 09:22:44 +0000 > > "Vincent Bray" <[EMAIL PROTECTED]> wrote: > > > > So I'm wondering what can be done about any of this. Perhaps: > > > > > > * Remove obsolete modules from the default build > > > * Reduce the size of the default config files > > The default config file for 2.2 is way reduced in size from earlier > versions. It could get a little smaller, but not much. > > > > The third option is the only one here I feel I can help with. Can I > > > have a show of hands on the idea of creating a section of the docs to > > > demonstrate minimal and specialist configurations? After all, there's > > > only *one* mandatory directive (Listen). > > I thought that was a primary purpose of the wiki. > > Joshua. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
