# HG changeset patch # User Nicolas Chauvat # Date 1285154494 -7200 # Node ID 3a87eaf226f60d8795cd385236087599a7e718f7 # Parent 228921b064c3963c4451ed0dc2b73b7942aa4cf5 [doc] fixing install doc (reapply cset that was erroneously overriden) diff -r 228921b064c3 -r 3a87eaf226f6 doc/book/en/admin/setup.rst --- a/doc/book/en/admin/setup.rst Wed Sep 22 17:01:51 2010 +0200 +++ b/doc/book/en/admin/setup.rst Wed Sep 22 13:21:34 2010 +0200 @@ -259,7 +259,7 @@ C:\\etc\\cubicweb.d. For a cube 'my_instance', you will then find -C:\\etc\\cubicweb.d\\my_instance\\win32svc.py that has to be used thusly:: +C:\\etc\\cubicweb.d\\my_instance\\win32svc.py that has to be used as follows:: win32svc install @@ -288,14 +288,17 @@ Databases configuration ----------------------- -Whatever the backend used, database connection information are stored in the -instance's :file:`sources` file. Currently cubicweb has been tested using -Postgresql (recommended), MySQL, SQLServer and SQLite. +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. Currently cubicweb has been tested +using Postgresql (recommended), MySQL, 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. SQLite is -not fit for production use, but it works for testing and ships with Python, -which saves installation time when you want to get started quickly. +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 +and ships with Python, which saves installation time when you want to get +started quickly. .. _PostgresqlConfiguration: