d99326d439
I'm going to change the recommended upgrade path from 2.0 to 2.1 to initialize a new site path and move everything over. This may require avoiding the auto-start of the daemon near the end. Change-Id: Id9d5b5b94d40b4c95c7b3a31796c943a8f684f76 Signed-off-by: Shawn O. Pearce <sop@google.com>
59 lines
1.4 KiB
Plaintext
59 lines
1.4 KiB
Plaintext
init
|
|
====
|
|
|
|
NAME
|
|
----
|
|
init - Initialize a new Gerrit server installation
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'java' -jar gerrit.war 'init'
|
|
-d <SITE_PATH>
|
|
[\--batch]
|
|
[\--import-projects]
|
|
[\--no-auto-start]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
Creates a new Gerrit server installation, interactively prompting
|
|
for some basic setup prior to writing default configuration files
|
|
into a newly created `$site_path`.
|
|
|
|
If run an an existing `$site_path`, init will upgrade some resources
|
|
as necessary. This can be useful to import newly created projects.
|
|
|
|
OPTIONS
|
|
-------
|
|
\--batch::
|
|
Run in batch mode, skipping interactive prompts. Reasonable
|
|
configuration defaults are chosen based on the whims of
|
|
the Gerrit developers.
|
|
|
|
\--import-projects::
|
|
Recursively search
|
|
link:config-gerrit.html#gerrit.basePath[gerrit.basePath]
|
|
for any Git repositories not yet registered as a project,
|
|
and initializes a new project for them.
|
|
|
|
\--no-auto-start::
|
|
Don't automatically start the daemon after initializing a
|
|
newly created site path. This permits the administartor
|
|
to inspect and modify the configuration before the daemon
|
|
is started.
|
|
|
|
-d::
|
|
\--site-path::
|
|
Location of the gerrit.config file, and all other per-site
|
|
configuration data, supporting libaries and log files.
|
|
|
|
CONTEXT
|
|
-------
|
|
This command can only be run on a server which has direct
|
|
connectivity to the metadata database, and local access to the
|
|
managed Git repositories.
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:index.html[Gerrit Code Review]
|