From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver][PATCH 7/7] hiawatha: add CONFFILES and a php example
Date: Mon, 26 Nov 2012 10:45:05 +0000 [thread overview]
Message-ID: <50B34831.10402@communistcode.co.uk> (raw)
In-Reply-To: <20121126113056.6385c072@eb-e6520>
On 26/11/12 10:30, Eric Bénard wrote:
> Hi Jack,
>
> Le Mon, 26 Nov 2012 10:27:26 +0000,
> Jack Mitchell <ml@communistcode.co.uk> a écrit :
>
>> On 25/11/12 17:25, Eric Bénard wrote:
>>> + # configure php-fcgi to have a working configuration
>>> + # by default if php is installed
>>> + echo "Server = ${bindir}/php-cgi ; 2 ; 127.0.0.1:2005 ; nobody:nobody ; ${sysconfdir}/php/hiawatha-php5/php.ini" >> ${D}${sysconfdir}/hiawatha/php-fcgi.conf
>>> }
>> Looks good to me, thanks for the improvements Eric!
>>
> I still have to find a good way to provide a default
> ${sysconfdir}/php/hiawatha-php5/php.ini and launch php-fcgi in the init
> script if php is enabled.
> Do you think we could provide the file php.ini in the hiawatha recipe
> (as hiawatha's doc recommends setting some options :
> http://www.hiawatha-webserver.org/howto/php_configuration ) ?
>
> Eric
The only way I could think of doing it would be to have some sort of
test to see if PHP is installed and then possibly sed the php.ini file
to set the correct values.
On the other hand, a note in the BB file may be enough and OE users
shouldn't really need their hands holding to this level.
As for the init file, I use PHP and Hiawatha as normal CGI rather than
using a fastCGI daemon, therefore I don't think it would be appropriate
to automatically start the fcgi daemon. We could possibly ship a
seperate fastCGI init file, although not automatically enable it?
Regards,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-11-26 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 17:25 [meta-webserver][PATCH 1/7] mysql: upgrade to 5.1.66 Eric Bénard
2012-11-25 17:25 ` [meta-webserver][PATCH 2/7] apache2: upgrade to 2.4.3 Eric Bénard
2012-11-25 17:25 ` [meta-webserver][PATCH 3/7] modphp: upgrade to 5.3.19 Eric Bénard
2012-11-25 17:25 ` [meta-webserver][PATCH 4/7] modphp: enable bz2, zip and mbstring Eric Bénard
2012-11-25 17:25 ` [meta-webserver][PATCH 5/7] php: upgrade to 5.3.19 Eric Bénard
2012-11-26 19:28 ` Martin Jansa
2012-11-25 17:25 ` [meta-webserver][PATCH 6/7] php: enable gettext and sqlite Eric Bénard
2012-11-25 17:25 ` [meta-webserver][PATCH 7/7] hiawatha: add CONFFILES and a php example Eric Bénard
2012-11-26 10:27 ` Jack Mitchell
2012-11-26 10:30 ` Eric Bénard
2012-11-26 10:45 ` Jack Mitchell [this message]
2012-11-26 10:48 ` Eric Bénard
2012-11-27 10:58 ` Paul Eggleton
2012-11-30 10:09 ` [meta-webserver][PATCH 1/7] mysql: upgrade to 5.1.66 Marcin Juszkiewicz
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=50B34831.10402@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@lists.openembedded.org \
/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.