10 - `PostgreSQL configuration`_ |
10 - `PostgreSQL configuration`_ |
11 - `MySql configuration`_ |
11 - `MySql configuration`_ |
12 - `SQLServer configuration`_ |
12 - `SQLServer configuration`_ |
13 - `SQLite configuration`_ |
13 - `SQLite configuration`_ |
14 |
14 |
15 For advenced features you can have a look to: |
15 For advanced features, have a look to: |
16 |
16 |
17 - `Pyro configuration`_ |
17 - `Pyro configuration`_ |
18 - `Cubicweb resources configuration`_ |
18 - `Cubicweb resources configuration`_ |
19 |
19 |
20 .. _`configure the database`: DatabaseInstallation_ |
20 .. _`configure the database`: DatabaseInstallation_ |
40 Databases configuration |
40 Databases configuration |
41 ----------------------- |
41 ----------------------- |
42 |
42 |
43 Each instance can be configured with its own database connection information, |
43 Each instance can be configured with its own database connection information, |
44 that will be stored in the instance's :file:`sources` file. The database to use |
44 that will be stored in the instance's :file:`sources` file. The database to use |
45 will be chosen when creating the instance. Currently cubicweb has been tested |
45 will be chosen when creating the instance. CubicWeb is known to run with |
46 using Postgresql (recommended), MySQL, SQLServer and SQLite. |
46 Postgresql (recommended), MySQL, SQLServer and SQLite. |
47 |
47 |
48 Other possible sources of data include CubicWeb, Subversion, LDAP and Mercurial, |
48 Other possible sources of data include CubicWeb, Subversion, LDAP and Mercurial, |
49 but at least one relational database is required for CubicWeb to work. You do |
49 but at least one relational database is required for CubicWeb to work. You do |
50 not need to install a backend that you do not intend to use for one of your |
50 not need to install a backend that you do not intend to use for one of your |
51 instances. SQLite is not fit for production use, but it works well for testing |
51 instances. SQLite is not fit for production use, but it works well for testing |
75 If you already have an existing cluster and PostgreSQL server running, you do |
75 If you already have an existing cluster and PostgreSQL server running, you do |
76 not need to execute the initilization step of your PostgreSQL database unless |
76 not need to execute the initilization step of your PostgreSQL database unless |
77 you want a specific cluster for |cubicweb| databases or if your existing |
77 you want a specific cluster for |cubicweb| databases or if your existing |
78 cluster doesn't use the UTF8 encoding (see note below). |
78 cluster doesn't use the UTF8 encoding (see note below). |
79 |
79 |
80 * First, initialize a PostgreSQL cluster with the command ``initdb``. |
80 * First, initialize a PostgreSQL cluster with the command ``initdb``:: |
81 :: |
|
82 |
81 |
83 $ initdb -E UTF8 -D /path/to/pgsql |
82 $ initdb -E UTF8 -D /path/to/pgsql |
84 |
83 |
85 Notice the encoding specification. This is necessary since |cubicweb| usually |
84 Notice the encoding specification. This is necessary since |cubicweb| usually |
86 want UTF8 encoded database. If you use a cluster with the wrong encoding, you'll |
85 want UTF8 encoded database. If you use a cluster with the wrong encoding, you'll |