Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > Feature Requests

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #11  
Old 18th May 2010, 13:20
Keeper Keeper is offline
Member
 
Join Date: Aug 2009
Posts: 42
Thanks: 0
Thanked 0 Times in 0 Posts
Default

If someone chooses nginx or lighttpd over apache, I'm fairly certain they have educated themselves of their features (or lack thereof).

As for htaccess, AFAIK they are mostly used for rewrite rules, to which both nginx and lighttpd provide modules. Now, said modules do not use htaccess files but you're able to replicate functionality of htaccess files.

Nginx and lighttpd might be light webservers, but this does not mean that they are not suitable for "normal" hosting as you put it. Exactly the opposite actually. Both of them provide enough features to set up complex virtual hosting with PHP, Ruby, you name it, without need for Apache.

The only caveat here is that while they provide the features, they are not necessarily Apache-compatible. Such as any Apache features relying on htaccess files. Still, in almost all cases you can replicate full functionality of htaccess files via their own respective features.

Them being light webservers is a misnomer really. What light means, is that they are fast, lean and mean webservers that are in most cases far more resource friendly than Apache. With alternative web servers you can potentially save up enormous amounts of memory and increase scalability beyond what Apache is able to.

This makes nginx and lighttpd top choices for people who have low-end servers or for people who are running very busy sites. Hell, they allow you to serve more users with same hardware as apache. And all this without having to sacrifice basic functionality you expect from web servers.

As for ISPConfig. Graying out unsupported features in ISPConfig interface would probably be more than enough for most people. That way you can add nginx or lighttpd specific features, which are then grayed out for apache users.

Last edited by Keeper; 18th May 2010 at 13:32.
Reply With Quote
Sponsored Links
  #12  
Old 18th April 2011, 18:45
StephenKing StephenKing is offline
Junior Member
 
Join Date: Apr 2011
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi,

I've set up a new server with ISPconfig and also played around with nginx. Together with php-fpm (see e.g. this tutorial), it works perfectly with TYPO3 and ~25-30% faster than Apache (while having ~40% lower memory consumption during a httperf stress test).

So I'd like to ask, what the current plans are. As ISPconfig pretends () to have a good plugin support, it should be easy to achieve, shouldn't it

I found the gitorious repository of "ispconfig-lite", which seems to bring nginx support. But I was not able to find any documentation or information regarding the state of the implementation.

Does anybody know, where the pitfalls of an nginx integration are?
I don't mind in some UI options being useless, as I configured the underlying server myself. IMHO most important things would be to write the sites-(enabled|available) file and restart the service. I don't expect more from a first implementation.

Thanks for your answer
Steffen
Reply With Quote
  #13  
Old 19th April 2011, 14:37
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,735 Times in 2,571 Posts
Default

There are currently no plans of integrating nginx or Lighttpd support.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #14  
Old 19th April 2011, 19:07
StephenKing StephenKing is offline
Junior Member
 
Join Date: Apr 2011
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for your answer, Falko.

Do you know sth. about the pitfalls or anybody else who is interested in developing such a plugin?

Steffen
Reply With Quote
  #15  
Old 19th April 2011, 19:16
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,476
Thanks: 813
Thanked 5,255 Times in 4,121 Posts
Default

The main problem that I see with such a plugin that neither lighttpd nor nginx is able to emulate all functions of a apache webserver. They are fast and a good choice for special purpose websites, but they can not fully replace apache on many setups. So several settings in the ispconfig interface will become useless and this might irritate cutsomers. E.g. when they add a rewrite rule which will not work or they try to use php modes and settings that are only available in apache. Especially .htaccess is a problem, as most cms system today come with htaccess files and thes efiles wont work anymore with lighttpd or ngincx. so your customers will call you to ask why their cms is not working as expected.

If you run a special purpose server e.g. as web agency and dont let your customers access the site settings and you dont need all functions that apache offers, then a lighttpd or nginx plugin might be a good choice.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #16  
Old 19th April 2011, 19:20
StephenKing StephenKing is offline
Junior Member
 
Join Date: Apr 2011
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Till,

as pointed out, if sb. chooses nginx, he probably knows, what he's doing. None of the clients on my server will configure it's domain himself. I like ISPconfig just to ease the process of creating new vhosts, mail accounts etc.

And as an administrator, I'd be fine for the beginning, having non-functional apache-only fields, when I'm running nginx.

What about moving the apache-specific fields to the apache plugin? It doesn't sound like it's this way currently (although I'd expect it from a plugin-based system).
Then deactivating the apache plugin would also remove all the related fields. Do you think that's an achievable task?

Steffen
Reply With Quote
  #17  
Old 19th April 2011, 19:39
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,476
Thanks: 813
Thanked 5,255 Times in 4,121 Posts
Default

Quote:
What about moving the apache-specific fields to the apache plugin? It doesn't sound like it's this way currently (although I'd expect it from a plugin-based system).
Then deactivating the apache plugin would also remove all the related fields. Do you think that's an achievable task?
The server and interface part are completely separated. The server part id completely based on plugins, the interface not. The interface supports plugins and also events, but the templates are files and not created on the fly, so they can not reflect such changes. Enabling or disabling a server plugin has no influence on the interface.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #18  
Old 1st June 2011, 13:37
shikar shikar is offline
Banned
 
Join Date: Jun 2011
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
 
Default

thanks for sharing
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 21:35.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.