equal
deleted
inserted
replaced
12 - `SQLServer configuration`_ |
12 - `SQLServer configuration`_ |
13 - `SQLite configuration`_ |
13 - `SQLite configuration`_ |
14 |
14 |
15 For advanced features, have a look to: |
15 For advanced features, have a look to: |
16 |
16 |
17 - `Pyro configuration`_ |
|
18 - `Cubicweb resources configuration`_ |
17 - `Cubicweb resources configuration`_ |
19 |
18 |
20 .. _`configure the database`: DatabaseInstallation_ |
19 .. _`configure the database`: DatabaseInstallation_ |
21 .. _`PostgreSQL configuration`: PostgresqlConfiguration_ |
20 .. _`PostgreSQL configuration`: PostgresqlConfiguration_ |
22 .. _`MySql configuration`: MySqlConfiguration_ |
21 .. _`MySql configuration`: MySqlConfiguration_ |
23 .. _`SQLServer configuration`: SQLServerConfiguration_ |
22 .. _`SQLServer configuration`: SQLServerConfiguration_ |
24 .. _`SQLite configuration`: SQLiteConfiguration_ |
23 .. _`SQLite configuration`: SQLiteConfiguration_ |
25 .. _`Pyro configuration`: PyroConfiguration_ |
|
26 .. _`Cubicweb resources configuration`: RessourcesConfiguration_ |
24 .. _`Cubicweb resources configuration`: RessourcesConfiguration_ |
27 |
25 |
28 |
26 |
29 |
27 |
30 .. _RessourcesConfiguration: |
28 .. _RessourcesConfiguration: |
227 |
225 |
228 .. Note:: |
226 .. Note:: |
229 SQLite is great for testing and to play with cubicweb but is not suited for |
227 SQLite is great for testing and to play with cubicweb but is not suited for |
230 production environments. |
228 production environments. |
231 |
229 |
232 |
|
233 .. _PyroConfiguration: |
|
234 |
|
235 Pyro configuration |
|
236 ------------------ |
|
237 |
|
238 Pyro name server |
|
239 ~~~~~~~~~~~~~~~~ |
|
240 |
|
241 If you want to use Pyro to access your instance remotely, or to have multi-source |
|
242 or distributed configuration, it is required to have a Pyro name server running |
|
243 on your network. By default it is detected by a broadcast request, but you can |
|
244 specify a location in the instance's configuration file. |
|
245 |
|
246 To do so, you need to : |
|
247 |
|
248 * be sure to have installed it (see :ref:`InstallDependencies`) |
|
249 |
|
250 * launch the pyro name server with `pyro-nsd start` before starting cubicweb |
|
251 |
|
252 * under debian, edit the file :file:`/etc/default/pyro-nsd` so that the name |
|
253 server pyro will be launched automatically when the machine fire up |
|
254 |
|
255 Note that you can use the pyro server without a running pyro nameserver. |
|
256 Refer to `pyro-ns-host` server configuration option for details. |
|
257 |
|