Production Use of Nginx / php-fpm54+

[DA DUDE]

Yesterday we (my company) setup our first DirectAdmin server running Nginx 1.4.1 and php-fpm54. The performance is great and content is definitely delivered MUCH faster.

However, as has been discussed briefly before, the lack of .htaccess for just about every CMS is concerning - especially with our hundreds of WordPress clients. I want to hear from folks using this setup on a production server with clients. How do you go about friendly permalinks? Do you find the setup having significant limitations at this point?

Some ideas for DA developers:

• Check if CMS is used during setup, if so setup permalink rewrites.

If you're curious about Nginx on Direct Admin and want to give it a try, PM me and I will create you an account at https://cp1.instovo.com:2222/ . No guarantees on when the test account will be deleted, 24 hour notice will be given. I hope you like the non-default login and signed SSL

 

[DA DUDE]

I would also like to add: at the moment it seems necessary to restart php-fpm54 every time a new domain is added in order for php to function properly.

 

[DirectAdmin Support]

Hello,

1) The php-fpm restart is a bug for now, we need to get DA to restart those services.

2) There is no doubt a need to support some sort of redirections or .htaccess related settings with nginx.
We do plan on adding support for those types of things as they're needed.
Note that the completion work on nginx in CB2 is going to be the last phase... apache, and all of the new php types will come first (they're almost done, just needs some minor polish), then there will time for the extra functionality in nginx.

John

 

[DA DUDE]

Hello,

1) The php-fpm restart is a bug for now, we need to get DA to restart those services.

2) There is no doubt a need to support some sort of redirections or .htaccess related settings with nginx.
We do plan on adding support for those types of things as they're needed.
Note that the completion work on nginx in CB2 is going to be the last phase... apache, and all of the new php types will come first (they're almost done, just needs some minor polish), then there will time for the extra functionality in nginx.

John

John: Thanks for taking the time to personally reply to my topic; I appreciate it. As much as we love nGinx, it appears that it may not the best setup right this minute.

I'm curious to know the rough amount of traffic / load one must have where nGinx actually shows a clear performance boost -- perhaps 30 concurrent connections on a low end box?

What new php types are you working on?

 

[DirectAdmin Support]

I've not personally done any benchmarks, but google can probably answer that for you.
We know that, because of it's slightly reduced feature set, that makes it much quicker (eg: no per-call file checks, like for .htaccess files.. all configs are right in the config)

CustomBuild 2 has support for mod_ruid2 + CLI, or FastCGI, or php-fpm. All new.
The default will be mod_ruid2 + CLI, as it's very stable (lots of testing already).. and has the performance benefit of CLI (vs suPhp).. but the security of running php as the User (unlike CLI without mod_ruid2)
The complexity level spikes up with FastCGI and php-fpm, so more issues can arise, but if setup correctly they're even faster.
For 90% of hosting boxes, mod_ruid2 + CLI will be plenty.

John

 

[DA DUDE]

The complexity level spikes up with FastCGI and php-fpm, so more issues can arise, but if setup correctly they're even faster.
For 90% of hosting boxes, mod_ruid2 + CLI will be plenty.

Thanks again John. Like I mentioned before, I'm using php-fpm54 right this moment (along with nginx). Obviously you will only release well tested php options, so what types of issues "could" arise? For the most case with php, it either works or it doesn't work, right?

 

[DirectAdmin Support]

Well.. if we knew, it wouldn't be called testing..
But things like strange timeouts, or extended features like directory password protection.. /roundcube, etc.. just all the functionality, above the standard parsing of php files.
If it works, it works.

John

 

[DA DUDE]

Well.. if we knew, it wouldn't be called testing..
But things like strange timeouts, or extended features like directory password protection.. /roundcube, etc.. just all the functionality, above the standard parsing of php files.
If it works, it works.
John

For sure Well thanks again and I look forward to searching for issues! Besides this forum, is there a tracker to report specific issues?

Also, thanks for the information about OS EOL, I look forward to having my license set to CentOS 6 32bit.