Re: [meta-webserver][PATCH 7/7] hiawatha: add CONFFILES and a php example

["Eric Bénard" <eric@eukrea.com>]

Le Mon, 26 Nov 2012 10:45:05 +0000,
Jack Mitchell <ml@communistcode.co.uk> a écrit :

> 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?

yes the idea is to provide default confi/init files which work so that
users can enable them with .bbappend in their overlay.

Eric