cubicweb: comparison doc/book/admin/config.rst

equal deleted inserted replaced

-:60369010c49e
+:dde85a5d47fc
 ==================================
 You can `configure the database`_ system of your choice:
 - `PostgreSQL configuration`_
-- `MySql configuration`_
 - `SQLServer configuration`_
 - `SQLite configuration`_
 For advanced features, have a look to:
 - `Cubicweb resources configuration`_
 .. _`configure the database`: DatabaseInstallation_
 .. _`PostgreSQL configuration`: PostgresqlConfiguration_
-.. _`MySql configuration`: MySqlConfiguration_
 .. _`SQLServer configuration`: SQLServerConfiguration_
 .. _`SQLite configuration`: SQLiteConfiguration_
 .. _`Cubicweb resources configuration`: RessourcesConfiguration_
 -----------------------
 Each instance can be configured with its own database connection information,
 that will be stored in the instance's :file:`sources` file. The database to use
 will be chosen when creating the instance. CubicWeb is known to run with
-Postgresql (recommended), SQLServer and SQLite, and may run with MySQL.
+Postgresql (recommended), SQLServer and SQLite.
 Other possible sources of data include CubicWeb, Subversion, LDAP and Mercurial,
 but at least one relational database is required for CubicWeb to work. You do
 not need to install a backend that you do not intend to use for one of your
 instances. SQLite is not fit for production use, but it works well for testing
 To initialize a PostgreSQL cluster, use the command ``initdb``::
 $ initdb -E UTF8 -D /path/to/pgsql
+Note: ``initdb`` might not be in the PATH, so you may have to use its
+absolute path instead (usually something like
+``/usr/lib/postgresql/9.4/bin/initdb``).
 Notice the encoding specification. This is necessary since |cubicweb| usually
 want UTF8 encoded database. If you use a cluster with the wrong encoding, you'll
 get error like::
 new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)
 If you cannot execute this command due to permission issues, please make sure
 that your username has write access on the database.  ::
 $ chown username /path/to/pgsql
 Database authentication
 +++++++++++++++++++++++
 The database authentication is configured in `pg_hba.conf`. It can be either set
 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 -P username
+$ createuser -s -P <dbuser>
 The option `-P` (for password prompt), will encrypt the password with the
 method set in the configuration file :file:`pg_hba.conf`.  If you do not use this
 option `-P`, then the default value will be null and you will need to set it
 with::
-$ su postgres -c "echo ALTER USER username WITH PASSWORD 'userpasswd' | psql"
+$ su postgres -c "echo ALTER USER <dbuser> WITH PASSWORD '<dbpassword>' | psql"
 The above login/password will be requested when you will create an instance with
 `cubicweb-ctl create` to initialize the database of your instance.
+Database creation
++++++++++++++++++
+If you create the database by hand (instead of using the `cubicweb-ctl
+db-create` tool), you may want to make sure that the local settings are
+properly set. For example, if you need to handle french accents
+properly for indexing and sorting, you may need to create the database
+with something like::
+$ createdb --encoding=UTF-8 --locale=fr_FR.UTF-8 -t template0 -O <owner> <dbname>
 Notice that the `cubicweb-ctl db-create` does database initialization that
 may requires a postgres superuser. That's why a login/password is explicitly asked
 at this step, so you can use there a superuser without using this user when running
 the instance. Things that require special privileges at this step:
 * database creation, require the 'create database' permission
-* install the plpython extension language (require superuser)
+* install the `plpython` extension language (require superuser)
-* install the tsearch extension for postgres version prior to 8.3 (require superuser)
 To avoid using a super user each time you create an install, a nice trick is to
 install plpython (and tsearch when needed) on the special `template1` database,
 so they will be installed automatically when cubicweb databases are created
-without even with needs for special access rights. To do so, run ::
+without needs for special access rights. To do so, run ::
 # Installation of plpythonu language by default ::
 $ createlang -U pgadmin plpythonu template1
 $ psql -U pgadmin template1
 template1=# update pg_language set lanpltrusted=TRUE where lanname='plpythonu';
 Where `pgadmin` is a postgres superuser. The last command is necessary since by
 default plpython is an 'untrusted' language and as such can't be used by non
 superuser. This update fix that problem by making it trusted.
-To install the tsearch plain-text index extension on postgres prior to 8.3, run::
-cat /usr/share/postgresql/8.X/contrib/tsearch2.sql | psql -U username template1
-.. _MySqlConfiguration:
-MySql
-~~~~~
-.. warning::
-CubicWeb's MySQL support is not commonly used, so things may or may not work properly.
-You must add the following lines in ``/etc/mysql/my.cnf`` file::
-transaction-isolation=READ-COMMITTED
-default-storage-engine=INNODB
-default-character-set=utf8
-max_allowed_packet = 128M
-.. Note::
-It is unclear whether mysql supports indexed string of arbitrary length or
-not.
 .. _SQLServerConfiguration:
 SQLServer
 anything for db-user and db-password, they will be ignore anyway.
 .. Note::
 SQLite is great for testing and to play with cubicweb but is not suited for
 production environments.

changeset 11338	dde85a5d47fc
parent 10491	c67bcee93248
child 12352	1a0159426def