From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] lighttpd: install fastcgi config for php
Date: Mon, 08 Dec 2014 01:19:27 +0100 [thread overview]
Message-ID: <5484EE8F.7030501@je-eigen-domein.nl> (raw)
In-Reply-To: <20141207235043.01177f0c@free-electrons.com>
On 12/07/2014 11:50 PM, Thomas Petazzoni wrote:
> Dear Ryan Coe,
>
> On Tue, 2 Dec 2014 14:35:24 -0800, Ryan Coe wrote:
>> Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
>> ---
>> package/lighttpd/fastcgi.conf | 7 +++++++
>> package/lighttpd/lighttpd.mk | 11 +++++++++++
>> 2 files changed, 18 insertions(+)
>> create mode 100644 package/lighttpd/fastcgi.conf
> Seeing the feedback from Floris Bos on this patch, I marked your patch
> as 'Rejected' in our patch tracking system. Please work with Floris on
> a variant of your patch that takes into account also his use case
> (maybe by making the fastcgi installation optional?).
Yes, a config option under the lighttpd package to optionally install
and configure PHP/FastCGI support might be nicer, instead of making the
assumption based on the selection of the PHP CGI SAPI.
You might also want to consider using PHP-FPM
That does allow using FastCGI while spawning/killing PHP processes
on-demand (instead of having a static number), so shouldn't suffer from
the problems I mentioned earlier.
But haven't tested it myself.
Another point of attention is that lighttpd currently runs as root.
Might want to add a less privileged user to the system to run
lighttpd/php under.
Yours sincerely,
Floris Bos
prev parent reply other threads:[~2014-12-08 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 22:35 [Buildroot] [PATCH 1/1] lighttpd: install fastcgi config for php Ryan Coe
2014-12-02 23:56 ` Floris Bos
2014-12-07 22:50 ` Thomas Petazzoni
2014-12-07 22:56 ` Ryan Coe
2014-12-08 0:19 ` Floris Bos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5484EE8F.7030501@je-eigen-domein.nl \
--to=bos@je-eigen-domein.nl \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.