# HG changeset patch # User Nicolas Chauvat # Date 1285154494 -7200 # Node ID 6794e3067f70d0a987b94ceeaffe9f34502a4977 # Parent 51a9494b5efbd82c98dd73d652da344bb364a944 [doc] fixing install doc diff -r 51a9494b5efb -r 6794e3067f70 doc/book/en/admin/setup.rst --- a/doc/book/en/admin/setup.rst Wed Sep 22 12:29:20 2010 +0200 +++ b/doc/book/en/admin/setup.rst Wed Sep 22 13:21:34 2010 +0200 @@ -274,7 +274,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 @@ -303,14 +303,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: