ISPCFG3 and nginx

[Ovidiu]

I have read countless threads, some trying to get it to work, others just using nginx as a front end proxy and now my question is:

Is it possible to get nginx fully supported? Is it just a question of time and money?

Honestly I spent at least a full week trying to get nginx working as a front end proxy and I am less than impressed with the results because my apache is still using way too much resources in the background.

I'd be more than willing to donate some money, so if Falko/Till are interested we could set up one of those fund-raising buttons and try to raise a sum that needs to be defined to get this done.

Please give me some feedback here.

[falko]

AFAIK, this is currently not on the ToDo list.

[Ovidiu]

:-( thats the reason I was asking...
because if it was about time/money that could have been solved, I am pretty sure about it...

Ok then, nevermind, will have to make another plan...

[theWeird]

There is already a feature request in ISPConfig3 Bugtracker.
You can vote for this task here:
http://bugtracker.ispconfig.org/inde...s&task_id=1017

[Ovidiu]

thanks will vote. This thread was to check if it is a question of time and or money.
I#d be willing to pay for such a feature and I am sure there are others who would pitch in to see this added.

Thanks for the link, will go vote.

[till]

The main problem that I see is that it will not be possible to implement all features with nginx that we crrently have for apache. So if nginx is used, there will be options in the website settings that will basically not work which will confuse the users. So using nginx might be an option for special purpose installs without client access that dont need all the redirect features and other things that rely on .htaccess and some other things that are available only as apache module.

[Ovidiu]

Ok, that makes sense.
let me add a related question: is there any other web server like lighttpd that could fully replace apache?

[till]

I'am not aaware of a replacement that has full .htaccess support.

The main problem with missing .htaccess support is that poeple rent a webspace, then e.g. install wordpress in it and without .htaccess support, things like the nice url extensions wont work and the the hosting provider will get the complaints that the webspace wornt wor.

There are some workarounds for ngingx an other servers, but as far as I know, they all use a different syntax and are not configured trough a simple drop-in file.

So we might support nginx in a lter version, but this will not be a complete replacement for apache. It will just be a faster alternative for servers that dont need all the apache features.

By the way, have you already tried to fine-tune your apache setup? There are large sites hosted on apache systems, so it should be possible to get a good and fast setup for most situations with apache as well.

[Ovidiu]

Ok, thanks for clarifying.
Currently its running stable with nginx as front end but I am not really happy.

Will post another apache tuning thread next year as I will be leaving for holiday tomorrow.

[theWeird]

Till, for apache optimisation, what do you think about the module pagespeed that has been published by google?