blob: d3094fdb3b0d9ef38e3a04044213c815844e271e [file] [log] [blame]
Shawn O. Pearce2fe738b2009-11-17 14:52:07 -08001init
2====
3
4NAME
5----
6init - Initialize a new Gerrit server installation
7
8SYNOPSIS
9--------
10[verse]
11'java' -jar gerrit.war 'init'
12 -d <SITE_PATH>
13 [\--batch]
Shawn O. Pearced99326d2009-12-14 07:34:04 -080014 [\--no-auto-start]
Shawn O. Pearce2fe738b2009-11-17 14:52:07 -080015
16DESCRIPTION
17-----------
18Creates a new Gerrit server installation, interactively prompting
19for some basic setup prior to writing default configuration files
20into a newly created `$site_path`.
21
22If run an an existing `$site_path`, init will upgrade some resources
Shawn O. Pearce89cefce2010-12-08 18:30:43 -080023as necessary.
Shawn O. Pearce2fe738b2009-11-17 14:52:07 -080024
25OPTIONS
26-------
27\--batch::
28 Run in batch mode, skipping interactive prompts. Reasonable
29 configuration defaults are chosen based on the whims of
30 the Gerrit developers.
31
Shawn O. Pearced99326d2009-12-14 07:34:04 -080032\--no-auto-start::
33 Don't automatically start the daemon after initializing a
34 newly created site path. This permits the administartor
35 to inspect and modify the configuration before the daemon
36 is started.
37
Shawn O. Pearce2fe738b2009-11-17 14:52:07 -080038-d::
39\--site-path::
40 Location of the gerrit.config file, and all other per-site
41 configuration data, supporting libaries and log files.
42
43CONTEXT
44-------
45This command can only be run on a server which has direct
46connectivity to the metadata database, and local access to the
47managed Git repositories.
48
49GERRIT
50------
51Part of link:index.html[Gerrit Code Review]