opendev/gerrit
Code Issues Proposed changes

Update Documentation of Auto Site Initialization

Browse Source 
Since the NotesMigration change, commit 220a3f5, it is no longer
possible to configure site_path in the database, with the system_config
table, during automatic site initialization. This commit updates the
documentation by removing references to this configuration option.

Change-Id: I3e4392991fb9d27c5306162353816759d2bbe577
This commit is contained in:
Reyad Attiyat
2017-02-28 08:55:06 -06:00
committed by David Pursehouse
parent 78eca63d86
commit ee59410153
1 changed files with 4 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
Documentation/config-auto-site-initialization.txt
View File

@@ -27,18 +27,10 @@ If the `gerrit.site_path` system property is defined then the init is
run for that site. The database connectivity, in that case, is defined run for that site. The database connectivity, in that case, is defined
in the `etc/gerrit.config`. in the `etc/gerrit.config`.
If `gerrit.site_path` is not defined then Gerrit will try to find an If `gerrit.site_path` is not defined then Gerrit will try to find the
existing site by looking into the `system_config` table in the database `gerrit.init_path` system property. If defined this property will be
defined via the `jdbc/ReviewDb` JNDI property. If the `system_config` used to determine the site path. The database connectivity, also for
table exists then the `site_path` from that table is used for the this case, is defined by the `jdbc/ReviewDb` JNDI property.
initialization. The database connectivity is defined by the
`jdbc/ReviewDb` JNDI property.
Finally, if neither the `gerrit.site_path` property nor the
`system_config` table exists, the `gerrit.init_path` system property,
if defined, will be used to determine the site path. The database
connectivity, also for this case, is defined by the `jdbc/ReviewDb`
JNDI property.
[WARNING] [WARNING]
Defining the `jdbc/ReviewDb` JNDI property for an H2 database under the Defining the `jdbc/ReviewDb` JNDI property for an H2 database under the
@@ -70,18 +62,6 @@ database is defined in `etc/gerrit.config` of that site:
=== Example 2 === Example 2
Prepare Tomcat so that an existing site with the path defined in the
`system_config` table is initialized (upgraded) on Gerrit startup. The
assumption is that the `jdbc/ReviewDb` JNDI property is defined in
Tomcat:
----
$ export CATALINA_OPTS='-Dgerrit.init'
$ catalina.sh start
----
=== Example 3
Assuming the database schema doesn't exist in the database defined Assuming the database schema doesn't exist in the database defined
via the `jdbc/ReviewDb` JNDI property, initialize a new site using that via the `jdbc/ReviewDb` JNDI property, initialize a new site using that
database and a given path: database and a given path: