207 .. _PyroConfiguration: |
207 .. _PyroConfiguration: |
208 |
208 |
209 Pyro configuration |
209 Pyro configuration |
210 ------------------ |
210 ------------------ |
211 |
211 |
|
212 Pyro name server |
|
213 ~~~~~~~~~~~~~~~~ |
212 If you want to use Pyro to access your instance remotely, or to have multi-source |
214 If you want to use Pyro to access your instance remotely, or to have multi-source |
213 or distributed configuration, it is required to have a Pyro name server running |
215 or distributed configuration, it is required to have a Pyro name server running |
214 on your network. By default it is detected by a broadcast request, but you can |
216 on your network. By default it is detected by a broadcast request, but you can |
215 specify a location in the instance's configuration file. |
217 specify a location in the instance's configuration file. |
216 |
218 |
217 To do so, you need to : |
219 To do so, you need to : |
218 |
220 |
|
221 * be sure to have installed it (see :ref:`InstallDependencies`) |
|
222 |
219 * launch the pyro name server with `pyro-nsd start` before starting cubicweb |
223 * launch the pyro name server with `pyro-nsd start` before starting cubicweb |
220 |
224 |
221 * under debian, edit the file :file:`/etc/default/pyro-nsd` so that the name |
225 * under debian, edit the file :file:`/etc/default/pyro-nsd` so that the name |
222 server pyro will be launched automatically when the machine fire up |
226 server pyro will be launched automatically when the machine fire up |
223 |
227 |
224 |
228 Note that you can use the pyro server without a running pyro nameserver. |
|
229 Refer to `pyro-ns-host` server configuration option for details. |
|
230 |