On 2014/05/07 12:30, Giovanni Bechis wrote:
> On 05/07/14 12:17, Stuart Henderson wrote:
> > On 2014/05/07 09:56, Giovanni Bechis wrote:
> >> Update to latest release, should we mention nginx instead of apache in 
> >> README now that we have no apache in base ?
> >>  Cheers & Thanks
> >>   Giovanni
> > 
> >> --- pkg/README     10 Sep 2012 09:16:34 -0000      1.1
> >> +++ pkg/README     7 May 2014 07:38:49 -0000
> >> @@ -8,7 +8,7 @@ Piwik has been installed into ${INSTDIR}
> >>  
> >>  You should point this to the DocumentRoot of your web-server:
> >>     # ln -s ../piwik /var/www/htdocs/piwik
> >> -(make sure you use a relative symlink since Apache is chrooted)
> >> +(make sure you use a relative symlink since Nginx is chrooted)
> > 
> > I don't think this is line is needed at all. The given symlink command
> > will work whether users use apache, nginx, lighttpd, or something else,
> > and whether or not it is chrooted, so it's just unnecessary information.
> > "Type this. Make sure you do the thing that the line we just told
> > you to type is already doing." (''oh, I've typed this, now do I have to
> > do something else to comply with the "make sure..." bit?'')
> > 
> >>  You will also need to add these lines to you php.ini file:
> >>      extension=pdo.so
> > 
> > This part is outdated - there is no pdo.so (at least for any of
> > the PHP version in our tree, if ever?) - php.ini has been replaced
> > with php-${MODPHP_VERSION}.ini - and extensions should be handled
> > by symlinking files from /etc/php-${MODPHP_VERSION}.sample into
> > /etc/php-${MODPHP_VERSION} (like the MESSAGE files already tell
> > you every time you update packages ;)
> > 
> ok, thanks.
> what about the apache specific files we have in some www ports (www/chive, 
> www/phpmyadmin, www/drupal7/core) ?
> Should they be removed or not ?
>  Cheers
>   Giovanni

I think they should be kept, some people still have a requirement to use
Apache (for example there's no good mod_perl alternative with nginx and
people may want to avoid running 2 separate web server programs).
But we should try to provide nginx information where possible.
(Somewhere on my to-do list is to try some of these files with apache2
and see if they work - but my to-do list is already too long ;-)


Reply via email to