|Subject:||Re: [nginx-announce] nginx-0.8.30|
|From:||Michael Shadle (mike...@gmail.com)|
|Date:||Dec 17, 2009 2:04:06 pm|
or just recipes on the wiki :)
On Thu, Dec 17, 2009 at 12:32 PM, merlin corey <merl...@dc949.org> wrote:
On Tue, Dec 15, 2009 at 6:36 PM, Michael Shadle <mike...@gmail.com> wrote:
Oh duh. :)
I actually have a lot less for my django setup than that even.
Sent from my iPhone
On Dec 15, 2009, at 5:48 PM, merlin corey <merl...@dc949.org> wrote:
On Tue, Dec 15, 2009 at 2:36 PM, Michael Shadle <mike...@gmail.com> wrote:
On Tue, Dec 15, 2009 at 7:21 AM, Igor Sysoev <ig...@sysoev.ru> wrote:
*) Feature: the conf/fastcgi.conf for simple FastCGI configurations.
What's the reasoning for this? Right now it's identical to fastcgi_params besides for no
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
Which I think should be kept as default, as it's probably the most standard way people use it, and they can overrfastide it manually in the server config if they choose to host PHP in some wacky place...
Because it's not just for PHP. Most other people don't NEED SCRIPT_FILENAME (or at least in my experience) and I think it's a good thing to not needlessly pass along a value made of variables that must be resolved.
That said I'll be including fastcgi.conf instead of fastcgi_params on my PHP boxes now :).
Yeah actually, we might want to start another thread about it and see what other people are doing, but I made a python_params that is basically like fastcgi.conf except it includes PATH_INFO instead of SCRIPT_FILENAME :-).