comparison docs/setup.rst @ 8592:307c876a6e89

db: introduce db-create --reuse option Support use of an existing database so the Kallithea database user doesn't have to be granted permissions to create databases. The existing database must of course have been created "correctly", for example using the right charset and collation on MariaDB/MySQL. Creating the database manually also provides a way to avoid the hardcoded defaults.
author Mads Kiilerich <mads@kiilerich.com>
date Thu, 25 Jun 2020 01:51:18 +0200
parents ff8651b2f14f
children 61bd04b90f58
comparison
equal deleted inserted replaced
8591:8759238d7356 8592:307c876a6e89
81 empty location, or a location which already contains existing 81 empty location, or a location which already contains existing
82 repositories. If you choose a location which contains existing 82 repositories. If you choose a location which contains existing
83 repositories Kallithea will add all of the repositories at the chosen 83 repositories Kallithea will add all of the repositories at the chosen
84 location to its database. (Note: make sure you specify the correct 84 location to its database. (Note: make sure you specify the correct
85 path to the root). 85 path to the root).
86
87 .. note:: It is also possible to use an existing database. For example,
88 when using PostgreSQL without granting general createdb privileges to
89 the PostgreSQL kallithea user, set ``sqlalchemy.url =
90 postgresql://kallithea:password@localhost/kallithea`` and create the
91 database like::
92
93 sudo -u postgres createdb 'kallithea' --owner 'kallithea'
94 kallithea-cli db-create -c my.ini --reuse
86 95
87 Prepare front-end files 96 Prepare front-end files
88 ^^^^^^^^^^^^^^^^^^^^^^^ 97 ^^^^^^^^^^^^^^^^^^^^^^^
89 98
90 Finally, the front-end files must be prepared. This requires ``npm`` version 6 99 Finally, the front-end files must be prepared. This requires ``npm`` version 6