272 |
272 |
273 This currently assumes that the instances configurations is located at |
273 This currently assumes that the instances configurations is located at |
274 C:\\etc\\cubicweb.d. |
274 C:\\etc\\cubicweb.d. |
275 |
275 |
276 For a cube 'my_instance', you will then find |
276 For a cube 'my_instance', you will then find |
277 C:\\etc\\cubicweb.d\\my_instance\\win32svc.py that has to be used thusly:: |
277 C:\\etc\\cubicweb.d\\my_instance\\win32svc.py that has to be used as follows:: |
278 |
278 |
279 win32svc install |
279 win32svc install |
280 |
280 |
281 This should just register your instance as a windows service. A simple:: |
281 This should just register your instance as a windows service. A simple:: |
282 |
282 |
301 .. _DatabaseInstallation: |
301 .. _DatabaseInstallation: |
302 |
302 |
303 Databases configuration |
303 Databases configuration |
304 ----------------------- |
304 ----------------------- |
305 |
305 |
306 Whatever the backend used, database connection information are stored in the |
306 Each instance can be configured with its own database connection information, |
307 instance's :file:`sources` file. Currently cubicweb has been tested using |
307 that will be stored in the instance's :file:`sources` file. The database to use |
308 Postgresql (recommended), MySQL, SQLServer and SQLite. |
308 will be chosen when creating the instance. Currently cubicweb has been tested |
|
309 using Postgresql (recommended), MySQL, SQLServer and SQLite. |
309 |
310 |
310 Other possible sources of data include CubicWeb, Subversion, LDAP and Mercurial, |
311 Other possible sources of data include CubicWeb, Subversion, LDAP and Mercurial, |
311 but at least one relational database is required for CubicWeb to work. SQLite is |
312 but at least one relational database is required for CubicWeb to work. You do |
312 not fit for production use, but it works for testing and ships with Python, |
313 not need to install a backend that you do not intend to use for one of your |
313 which saves installation time when you want to get started quickly. |
314 instances. SQLite is not fit for production use, but it works well for testing |
|
315 and ships with Python, which saves installation time when you want to get |
|
316 started quickly. |
314 |
317 |
315 .. _PostgresqlConfiguration: |
318 .. _PostgresqlConfiguration: |
316 |
319 |
317 PostgreSQL configuration |
320 PostgreSQL configuration |
318 ```````````````````````` |
321 ```````````````````````` |