LÖVE

Hey!

You may have noticed the site just went for a minute or two. That was because I was setting up php-fpm, which is a FastCGI manager thing that is 500x more awesome and working than my previous solution (hint: it involved while loops and pgrep).

The result of this short downtime: There shouldn't be any more 502 errors, since the CGI stuff will be handled professionally.

Hurray!

FastCGI FTW.

Thanks for taking the time to do it.

I thought you said the only way to fix PHP was called Python/Perl/Ruby/Lua?

nevon wrote:I thought you said the only way to fix PHP was called Python/Perl/Ruby/Lua?

That point still stands. The PHP CGI handlers are still dying. This is just a more effective way of reviving them.

thelinx wrote:

nevon wrote:I thought you said the only way to fix PHP was called Python/Perl/Ruby/Lua?

That point still stands. The PHP CGI handlers are still dying. This is just a more effective way of reviving them.

Did you poison them or something? :/

Nah, it's just PHP being PHP.

thelinx wrote:Nah, it's just PHP being PHP.

My grandfather used to work at NASA as a PHP programmer.

I like the lack of Gateway 502 errors anymore.