# HG changeset patch # User Emile Anclin # Date 1238607757 -7200 # Node ID 944dacbb16cad3281c7dc6337f98e07bb719ec16 # Parent 33d0e08a931a872fd08891db64d0cb93090dc1fb# Parent 746b83d492bb606637d8624cc23a58f00e71c5f3 merge diff -r 33d0e08a931a -r 944dacbb16ca doc/book/en/C011-installation.en.txt --- a/doc/book/en/C011-installation.en.txt Wed Apr 01 19:40:51 2009 +0200 +++ b/doc/book/en/C011-installation.en.txt Wed Apr 01 19:42:37 2009 +0200 @@ -29,7 +29,7 @@ deb http://ftp.logilab.org/dists/ hardy/ -You can now install the required packages with the following command:: +You can now install the required packages with the following command: :: apt-get update apt-get install cubicweb @@ -41,7 +41,7 @@ Install from source ``````````````````` -You can download the archive containing the sources from our `ftp site`_ at:: +You can download the archive containing the sources from our `ftp site`_ at: :: http://ftp.logilab.org/pub/cubicweb/ @@ -92,8 +92,8 @@ Your new cubes will be placed in `/usr/share/cubicweb/cubes` and your applications will be placed in `/etc/cubicweb.d`. -To use other directories you will have to configure the -following environment variables as follows:: +To use others directories then you will have to configure the +following environment variables as follows: :: export CW_CUBES_PATH=~/lib/cubes export CW_REGISTRY=~/etc/cubicweb.d/ @@ -111,7 +111,7 @@ .. note:: If you already have an existing cluster and postgres server - running you do not require to execute the initilization step + running, you do not require to execute the initilization step of your Postgres database. * First you have to initialize the database Postgres with the command ``initdb``. @@ -120,7 +120,7 @@ $ initdb -D /path/to/pgsql Once initialized, you can launch the database server Postgres - with the command:: + with the command: :: $ postgres -D /path/to/psql @@ -130,20 +130,30 @@ $ chown username /path/to/pgsql -* Create a superuser for `CubicWeb` instance:: +* The database authentication can be either set to `ident sameuser` + or `md5`. + If set to `md5`, make sure to use an existing user + of your database. + If set to `ident sameuser`, make sure that your + client's operating system user name has a matching user in + the database. If not, please do as follow to create a user: :: $ su $ su - postgres $ createuser -s username - Initialize the password of the superuser you just created for your - database:: + If created with the options -P (for password prompt, + ``createuser -s -P username``), the password will be encrypted with + the method set in the configuration file ``pg_hba.conf``. + If you do not use this option, then the default value will be null + and this require to set the password in the database itself. + To do so: :: $ su $ su - postgres $ psql - And then execute de following query:: + And then execute de following query: :: ALTER USER username WITH PASSWORD `password` @@ -151,6 +161,10 @@ instance with `cubicweb-ctl create` to initialize the database of your application. +.. note:: + The authentication method can be configured in ``pg_hba.conf``. + + .. FIXME Are these steps really necessary? It seemed to work without. * installation of plain-text index extension :: diff -r 33d0e08a931a -r 944dacbb16ca interfaces.py --- a/interfaces.py Wed Apr 01 19:40:51 2009 +0200 +++ b/interfaces.py Wed Apr 01 19:42:37 2009 +0200 @@ -246,12 +246,26 @@ """return content entity""" def isioc_container(self): - """return container entity""" + """return container entity""" + + def isioc_type(self): + """return container type (post, BlogPost, MailMessage)""" + + def isioc_replies(self): + """return replies items""" + + def isioc_topics(self): + """return topics items""" class ISiocContainer(Interface): """interface for entities (which are container in sioc specification) with sioc views""" def isioc_type(self): - """return container type (forum, weblog, mailinglist)""" + """return container type (forum, Weblog, MailingList)""" + + def isioc_items(self): + """return contained items""" + +