[Spip-maintainers] Bug#612467: spip: Incomplete install documentation

[Olivier Berger]

On Tue, 06 Dec 2011 10:04:41 -0400, David Prévot <david at tilapin.org> wrote:
> Hi,
> 
> Le 06/12/2011 06:10, Olivier Berger a écrit :
> > On Tue, Feb 08, 2011 at 05:31:28PM +0100, Romain DOUMENC wrote:
> >>
> >> After a fresh installation via apt-get, the documentation (as given by the file
> >> README.Debian) is rather not sufficient for me (and I assume I am not alone in 
> >> this case...).
> > 
> > I do agree the instructions are a bit too scarce, even though that's not uncommon WRT Debian web apps packaging.
> > 
> >> Would it be possible to change this file for something like :
> >>
> >> 1. Copy /etc/spip/apache.conf to /etc/apache2/sites-available/spip
> 
> It's actually /usr/share/doc/spip/apache2.conf that should be copied to
> /etc/apache2/sites-available/http-host (http-host to follow the actual
> logic in the current README file).
> 

I'm not sure I understand... what's the point of /etc/spip/apache.conf,
then ?

AFAIU, there's either one file, /etc/spip/apache.conf that may be
included inside an existing enabled site config file (in the case
several web apps have to coexist inside the same apache virtual host, as
I explained below), or that /usr/share/doc/spip/apache2.conf that could
be used as a dedicated virtual host, for a2ensite ?

> >> 2. Run a2ensite spip
> 
> s/spip/http-host/
> 

I find these instructions quite confusing : what's the words "http-host" here ?

AFAIU, the idea would be that several SPIPs are possibly installed on
the same apache, each with a dedicated "host name", for which different
/var/lib/spip/sites/ would be setup ? 

In such case, the README.Debian, mentioning "http-host" should maybe
explicit that http-host has to be replaced by whatever the admin wants
depending on the local installation ?

But, it doesn't seem to me that running spip_add_site is needed for a
basic default install, where apache would run one single instance of
SPIP, right ?

> >> 3. Check that spip has a user access to a mysql database
> >> 4. Point your browser to spipsite/ecrire
> > 
> > I'm not sure this is the best way to go, in particular if several web apps are co-located on the same apache server.
> > 
> > I'd advise instead to add an :
> >    Include /etc/spip/apache.conf
> > inside the virtualhost config in /etc/apache2/sites-enabled/000-default...
> 
> /etc/apache2/conf.d/spip.conf is already a link to that file.

OK, so, maybe this one, yes, in the Include directive, (kinda policy
like location).

> 
> > Then, I'm puzzled by the :
> >   # Uncomment this to add an alias.
> >   # This does not work properly with virtual hosts..
> >   # Alias /spip /var/lib/spip
> > in /etc/spip/apache.conf, as I have it just working now inside the default <VirtualHost *:80>...
> 
> The purpose of the proposed Alias is to make SPIP available from
> http://<hostanme>/spip (where hostname is anything that point to the
> host, no matter what VirtualHost it is). I guess Romain added this
> before he added the mutualisation, so that proposed Alias and its
> comment should be safely dropped.
> 

Hmmm... and that "mutualisation" thing should be profficiently
documented in the README.Debian, then ;)

Thanks for the feedback.
-- 
Olivier BERGER 
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)