Filed with Developers nginx for accelerating Apache [Case 41719]

[AlexAT]

David, maybe solution is to have several types of user accounts?
1st type - apache account (like all accounts are now).
2nd type - nginx account (all pages of this account served by nginx).
3rd type - something-to-be-added-in-future account

?

All "apache" account files will be served by apache.
All "nginx" account files will be served by nginx.

Customers that need fast speed will switch from apache to nginx account's type (reseller or root will perform this switch for them).
Those customers will be noted that they will loose .htaccess support, custom password support etc.

So each customer will have possibility to choose what it needs.
And each root will have possibility to set nginx or apache as primary web-server - all new account will be created with this type of account.

Is it possible?
If so - this will be more than GREAT!

[cPanelDavidG]

David, maybe solution is to have several types of user accounts?
1st type - apache account (like all accounts are now).
2nd type - nginx account (all pages of this account served by nginx).
3rd type - something-to-be-added-in-future account

?

All "apache" account files will be served by apache.
All "nginx" account files will be served by nginx.

Customers that need fast speed will switch from apache to nginx account's type (reseller or root will perform this switch for them).
Those customers will be noted that they will loose .htaccess support, custom password support etc.

So each customer will have possibility to choose what it needs.
And each root will have possibility to set nginx or apache as primary web-server - all new account will be created with this type of account.

Is it possible?
If so - this will be more than GREAT!

Seems much more feasible and less troublesome than the Apache-accelerated by nginx scenario.

I'm just curious on a technical level, how would one have two daemons serving traffic on port 80 in this scenario? Would there have to be a third daemon to direct traffic, or would this best be handled using "fallthrough" models many proposed where one daemon is the primary and any requests it is not handling simply falls through to the other daemon?

[AlexAT]

Seems much more feasible and less troublesome than the Apache-accelerated by nginx scenario.

I'm just curious on a technical level, how would one have two daemons serving traffic on port 80 in this scenario? Would there have to be a third daemon to direct traffic, or would this best be handled using "fallthrough" models many proposed where one daemon is the primary and any requests it is not handling simply falls through to the other daemon?

Best scenario (from experience) - to get nginx as frontend (port 80) and apache as backend (any other port).
It's very easy to setup and this solution has pretty good performance.

So all nginx type accounts can be handled directly by nginx - very fast.
And for all apache accounts nginx should work as clean proxy - also will be very fast since nginx utilize small amount of resources and do it very fast.

BTW - many cPanel server owners use this way of setup for years. And it'll be good to integrate it officially.

[Avanti]

I'm just curious on a technical level, how would one have two daemons serving traffic on port 80 in this scenario?

What about IP addresses dedicated to nginx or apache. For example, 1.2.3.4:80 would have apache listingin and 1.2.3.5:80 would have nginx listening.
Only problem I can see with this is that a moving a website from apache to nginx or vice versa would include a change of IP address... Maybe not actually such a good idea.

Maybe AlexAT's idea is better

[DomineauX]

Best scenario (from experience) - to get nginx as frontend (port 80) and apache as backend (any other port).
It's very easy to setup and this solution has pretty good performance.

So all nginx type accounts can be handled directly by nginx - very fast.
And for all apache accounts nginx should work as clean proxy - also will be very fast since nginx utilize small amount of resources and do it very fast.

BTW - many cPanel server owners use this way of setup for years. And it'll be good to integrate it officially.

Agreed, this is how most have done it for years. Nginx listening on port 80 and completely handles serving static content and what it can without trouble, and proxies requests to Apache for stuff it cannot handle well or is simply configured to not serve itself.

[egillette]

That can be solved with a patch, and that patch is provided in another thread at the central cpanel forum.

For me i would like to see 3 options:
1) apache only
2) nginx + apache
3) nginx only (with the related phpfm or spawn-fcgi)

What i'm using now, is nginx+apache, and the results are super, the load is almost zero, where in the past was near 2 and upper.

I 2nd xanubi on this. . .I think giving 3 separate and distinct options/explanations to the server admin would be incredibly helpful and beneficial. =0)

[vinodchacko]

Moderator edit: Forked from post with numerous requests
I am aware of some cPanel servers which are hosting more than 1500 cpanel accounts. And given that Apache have a larger memory foot print, why we should use it to drive images which need nothing else just a web server ? cpnginx.com is providing such a plugin. So is unixy.net‘s varnish plugin ( this actually is a reverse proxy and caching ).

[Datcrack]

We are very much looking forward to this. Nginx on the frontend and apache on the back would be ideal. Serving static files with nginx is excellent. However there is the problem of .htaccess usage which nginx does not support.

[egillette]

Actually,

It is quite easy to get .htaccess files processed.

In your nginx.conf file, simply add the following line:

ssi on;

That will allow your .htaccess files to be processed as usual.

I know this works for a fact, since I have nginx running on all 9 of my servers, and many of them have .htaccess directives, and they work flawlessly.

I don't think nginx directly supports .htaccess files, but turning on that directive makes nginx process the files natively through Apache when Apache is on the back-end as in the case of nginxcp.com.

Works fine for me.