Perhaps in a little bit - however, I don't supervise php-fpm with anything. If you're referencing something I said in the past about using upstart, that was in combination directly with php -b $port I had one file per pool I think I've posted that somewhere on the net, I can't find it right now. But I'm all about transparency (as long as it still retains privacy) Note I am using php 5.2.11 w/by mike - Nginx Mailing List - English
On Tue, Dec 8, 2009 at 6:21 PM, nerdgrind <nginx-forum@nginx.us> wrote: > I respect your'e opinions, but for all you're heated desperation to defend php-fcgi you may have forgotten this thread was started by someone who found php-fcgi to be unstable, and he hasn't been able to find a solution. I found one that worked for me when php-fcgi failed. Offering a solution to someone that resultby mike - Nginx Mailing List - English
On Tue, Dec 8, 2009 at 5:23 PM, fixxxer <fixxxerrr@gmail.com> wrote: > On 9 дек, 03:55, Michael Shadle <mike...@gmail.com> wrote: >> [..] > > conference talks, petitions? ok, but no result. now it's commited onto > a branch. people writing code? it's the php dev team now. outdated? in > php.internals you've just admitted you did not even test 0.6 yourself. Corrby mike - Php-fpm Mailing List - English
On Tue, Dec 8, 2009 at 4:46 PM, nerdgrind <nginx-forum@nginx.us> wrote: > Apache is rock solid. That's a fact. Keep reading to see how many web sites support this fact. It is stable, yes. Does it scale as well? No. > php-fcgi is unstable, and unreliable. That's a fact. It's no joke when a web site goes down on a production server. Down time is lost money. PLEASE give me these thousby mike - Nginx Mailing List - English
On Tue, Dec 8, 2009 at 4:39 PM, fixxxer <fixxxerrr@gmail.com> wrote: > sorry but who the hell you are to decide what the php dev group and > what they should not? why are you going to care about php release > cycles when you committed 0 lines of code? they bring no difference in > sending floods and facebook from your iphone. Who am I? I am the one that Andrei passed along theby mike - Php-fpm Mailing List - English
php-fpm handles millions of requests a day for me without an issue. Apache cannot handle the load on the same hardware. Go figure. FCGI for PHP is not only stable but time tested as well. You'll note that Zeus, lighttpd, nginx, almost every webserver with a user base sans litespeed and Apache can *only* use PHP over fastcgi. PHP-FPM isn't for everyone but soon can be. I gave my (as Norsek pointby mike - Nginx Mailing List - English
This boggles my mind. Apache just for php... Sent from my iPhone On Dec 8, 2009, at 1:43 PM, "nerdgrind" <nginx-forum@nginx.us> wrote: > You could use Apache to serve PHP scripts rather than spawn-fcgi/php- > cgi. Apache's handling of PHP has been time tested, and performs as > well or better than fcgi in my experience on a high traffic > Wordpress blog. > &gby mike - Nginx Mailing List - English
> On Tue, Dec 8, 2009 at 3:55 AM, Grzegorz Nosek <grzegorz.nosek@gmail.com> wrote: Once again, you've enhanced my statement. You're right. I've been discussing random php-fpm stuff on IRC and such and was thinking spawn-fcgi actually -did- something additional that php-cgi -b didn't do and had some php guts in it or something. Time to go to bed :) ______________________________________by mike - Nginx Mailing List - English
roger that. just wondering why they're crashing under spawn-fcgi to begin with. and also ... we all know php-fpm is a process manager too. two birds with the same stone! ;) On Tue, Dec 8, 2009 at 3:45 AM, Grzegorz Nosek <grzegorz.nosek@gmail.com> wrote: > On Tue, Dec 08, 2009 at 03:33:05AM -0800, Michael Shadle wrote: >> well spawn-fcgi not working properly could be considered criby mike - Nginx Mailing List - English
well spawn-fcgi not working properly could be considered critical. have you tried the latest stable spawn-fcgi, and then the latest beta? On Tue, Dec 8, 2009 at 3:29 AM, miradev <nginx-forum@nginx.us> wrote: > mike Wrote: > ------------------------------------------------------- >> Use php-fpm instead :) > > This would require re-compiling PHP, which I am not prepared toby mike - Nginx Mailing List - English
Use php-fpm instead :) On Tue, Dec 8, 2009 at 12:17 AM, miradev <nginx-forum@nginx.us> wrote: > Apologies if this is too off topic. My problem is not directly related to nginx. > > We've been running nginx + spawn-fcgi for 6 months without any issues. Until one morning I come in and all our sites are down because there were no php-cgi processes running. Obviously I'm keen to not haby mike - Nginx Mailing List - English
On Sat, Dec 5, 2009 at 9:28 PM, nerdgrind <nginx-forum@nginx.us> wrote: > I run Red Hat Enterprise Linux 5 server. If I were to install PHP-FPM, which patches the PHP package, it would be replaced when PHP is updated on the next yum update. I have spawn-cgi installed, and can run it only from the command line as such: well you don't run php from an rpm package and php-fpm on top of it.by mike - Nginx Mailing List - English
I can't speak for supercache, other people use it here with nginx, but WHY would you proxy to Apache for PHP? :) Take Apache out of the mix, you're wasting resources. Use PHP-FPM, spawn-fcgi, or php -b. Why have an entire webserver daemon and its overhead around just to parse PHP files. As far as supercache rewrites/configuration/etc. in nginx, there's been previous threads. All I know is I am uby mike - Nginx Mailing List - English
On Sat, Dec 5, 2009 at 4:30 PM, egerci <nginx-forum@nginx.us> wrote: > The problem is giving trust/certificate to company that behave or take action like me! > This show SL's understanding of Security. who would you believe more: a) your friend of 3 years b) someone off the street you're the one who originally got exploited. why would they trust you more than someone who they'veby mike - Nginx Mailing List - English
btw you can have the same file parsed for SSI and PHP :) neat little trick i realized which was nice, since one of my clients' sites was designed that way (don't ask...) On Sat, Dec 5, 2009 at 4:10 PM, Oleg Terenchuk <litwol@gmail.com> wrote: > Hello. > > According to english wiki, named locations may be used for other > purposes than fallback : > http://wiki.nginx.org/Nginxby mike - Nginx Mailing List - English
On Sat, Dec 5, 2009 at 1:30 PM, Steve <steeeeeveee@gmx.net> wrote: > And how would a Web UI have prevented that panic mode? See below - this isn't just web UI, but I see it as a chance to someone re-architect it a bit better. First, match feature set. Second, improve and adjust. > I think it would take you ages to get mailman to be on par with the possibilities a full blown up MTA iby mike - Nginx Mailing List - English
On Sat, Dec 5, 2009 at 1:58 PM, Steve <steeeeeveee@gmx.net> wrote: > Then Softlayer does not understand anything about security. Security is not a tool nor is it something you apply once and then forget about it. Security is a process. You need constantly to take care of it. Some time it is technical (hardware that can be installed, software that can be hardened, etc) and some time it isby mike - Nginx Mailing List - English
Note this has gotten wayyyy OT. On Sat, Dec 5, 2009 at 3:20 AM, Steve <steeeeeveee@gmx.net> wrote: >> mailman is a pain in the ass to install, >> > Mailman is not hard to install. Normally you just execute one command from your distro and the package is installed. Configuration is another issue. Sorry you're right. "Installing" it to me means not just unpacking orby mike - Nginx Mailing List - English
On Sat, Dec 5, 2009 at 1:54 AM, Jean-Baptiste Quenot <jbq@caraldi.com> wrote: > That sounds weird to me, rewriting Mailman in PHP. Mailman is an > excellent piece of software. If you need FastCGI support for Mailman, > why not hire a developer to implement that? With the excellent python > flup library, this will not be a daunting task. mailman is a pain in the ass to insby mike - Nginx Mailing List - English
2009/12/5 Jérôme Loyet <ml@fatbsd.com>: > Even if I think the same way as you, I think this is not so bad. We > have now an official integration into PHP and we can go forward safely > which is the most important thing for me. > > There is many things to do: > 1- check this version and confirm it works as expected (and correct it > if needed) > 2- See with the phpby mike - Php-fpm Mailing List - English
On Fri, Dec 4, 2009 at 5:16 AM, pcdinh <pcdinh@gmail.com> wrote: > Hi, > > Antony Dovgal, one of core PHP developers has just made an > announcement that FPM (without PHP) has become an official PHP > project. Here is the full text of that announcement This was totally out of left field, I was talking to another PHP core dev about whether or not it should be a new SAPI or bolby mike - Php-fpm Mailing List - English
it's just easier to maintain status quo. more people at my work are used to apache already. :) On Thu, Dec 3, 2009 at 9:53 PM, Igor Sysoev <igor@sysoev.ru> wrote: > On Thu, Dec 03, 2009 at 02:01:21PM -0800, Michael Shadle wrote: > >> Yah. I tried thttpd but it crashed on me randomly. Apache is stable. >> Works good enough. And the machines I use it on have more than enouby mike - Nginx Mailing List - English
On Thu, Dec 3, 2009 at 3:03 PM, Steve <steeeeeveee@gmx.net> wrote: > What? Because of mailman you run Apache? Well... I do run mailman 2.1.12 here on top of nginx 0.8.29 without any issues. No Apache involved in any way. I don't see any reason to use Apache for mailman. yeah - CGI-based stuff i run apache behind nginx for those couple things. i always have nginx on the frontend. how doby mike - Nginx Mailing List - English
Yah. I tried thttpd but it crashed on me randomly. Apache is stable. Works good enough. And the machines I use it on have more than enough resources. It'd be nice if nginx could do cgi :p I have to support mailman and bugzilla. Both seem archaic. One reason I am actually starting a php mailman replacement since there are literally only 3-4 mail list managers out there. None are simple tby mike - Nginx Mailing List - English
Using apache for anything if you don't need to if nginx will do it for you is a waste of resources and complicates your setup. I only use apache for mod_dav_svn, and cgi. Of which I am trying to minimize that impact by getting mailman ported to php :) Sent from my iPhone On Dec 3, 2009, at 11:55 AM, "egerci" <nginx-forum@nginx.us> wrote: > I use vbulletin. > You are rby mike - Nginx Mailing List - English
make another server block, use server_name 123.45.678.9; (if the catchall should be something different) On Wed, Dec 2, 2009 at 2:19 AM, Varix <nginx-forum@nginx.us> wrote: > Hallo, > > I want to use a folder like this > > http://123.45.678.9/photos/blabla.jpg > > > I have a default vhost to catch all > > server { > listen 80 default; >by mike - Nginx Mailing List - English
Use a different fastcgi port or socket per pool and each pool has it's own uid in php-fpm for example. Sent from my iPhone On Dec 2, 2009, at 12:39 AM, "d2" <nginx-forum@nginx.us> wrote: > Hi, > > Is there a way to configure vhost in nginx to run php scripts > (fastcgi gateway) with given UID? > So, despite that we deine user , virtualhost definition overrideby mike - Nginx Mailing List - English
there has been interest in a mod_svn or something of that nature from many people. i think it could be done just by implementing these extra http verbs required for webdav. (not 100% sure, but i know that those missing are not helping) i for one would be very interested in this (mainly so i can do svn through nginx, in fact, i have a request right now to implement svn over https and it's makingby mike - Nginx Mailing List - English
Okay, well this doesn't sound like a "bug" if there is a workaround; it's more of an "annoyance" that can hopefully be fixed. I am trying to figure out how to create a grid on the download page right now of PHP versions and their corresponding PHP-FPM versions (where applicable) Also, installation notes which should include things like this - specific instructions for differeby mike - Php-fpm Mailing List - English
I'll see if I can help when I get home on a cent machine.a Sent from my iPhone On Nov 27, 2009, at 8:53 PM, "wolfenstock" <nginx-forum@nginx.us> wrote: > I have installed php-fpm before with 5.2.10 before it was moved to > laundpad. I'm trying to install the 5.2.11 patch on my vps using > the readme.markdown integrated step and it fails when it cannot find > lby mike - Php-fpm Mailing List - English
![]() |
![]() |
![]() |
![]() |
|