summaryrefslogtreecommitdiffstats
path: root/Documentation/install.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/install.txt')
-rw-r--r--Documentation/install.txt70
1 files changed, 5 insertions, 65 deletions
diff --git a/Documentation/install.txt b/Documentation/install.txt
index 9926b8fd0c..4b14ff0bba 100644
--- a/Documentation/install.txt
+++ b/Documentation/install.txt
@@ -1,5 +1,5 @@
-Gerrit Code Review - Installation Guide
-=======================================
+Gerrit Code Review - Standalone Daemon Installation Guide
+=========================================================
[[requirements]]
Requirements
@@ -29,67 +29,7 @@ rename the downloaded file.
If you would prefer to build Gerrit directly from source, review
the notes under link:dev-readme.html[developer setup].
-
-[[createdb]]
-Database Setup
---------------
-
-[[createdb_h2]]
-H2
-~~
-
-During the init phase of Gerrit you will need to specify which database to use.
-If you choose H2, Gerrit will automatically set up the embedded H2 database as
-backend so no set up in advance is necessary. Also, no additional configuration is
-necessary. Using the embedded H2 database is the easiest way to get a Gerrit
-site up and running, making it ideal for proof of concepts or small team
-servers. On the flip side, H2 is not the recommended option for large
-corporate installations. This is because there is no easy way to interact
-with the database while Gerrit is offline, it's not easy to backup the data,
-and it's not possible to set up H2 in a load balanced/hotswap configuration.
-
-
-If this option interests you, you might want to consider link:install-quick.html[the quick guide].
-
-[[createdb_postgres]]
-PostgreSQL
-~~~~~~~~~~
-
-This option is more complicated than the H2 option but is recommended
-for larger installations. It's the database backend with the largest userbase
-in the Gerrit community.
-
-Create a user for the web application within Postgres, assign it a
-password, create a database to store the metadata, and grant the user
-full rights on the newly created database:
-
-----
- createuser -A -D -P -E gerrit2
- createdb -E UTF-8 -O gerrit2 reviewdb
-----
-
-
-[[createdb_mysql]]
-MySQL
-~~~~~
-
-This option is also more complicated than the H2 option. Just as with
-PostgreSQL it's also recommended for larger installations.
-
-Create a user for the web application within the database, assign it a
-password, create a database, and give the newly created user full
-rights on it:
-
-----
- mysql
-
- CREATE USER 'gerrit2'@'localhost' IDENTIFIED BY 'secret';
- CREATE DATABASE reviewdb;
- ALTER DATABASE reviewdb charset=latin1;
- GRANT ALL ON reviewdb.* TO 'gerrit2'@'localhost';
- FLUSH PRIVILEGES;
-----
-
+include::database-setup.txt[]
[[init]]
Initialize the Site
@@ -185,8 +125,8 @@ background, use the rc.d style start script created by 'init':
automatically starts and stops with the operating system:
====
- sudo ln -snf `pwd`/review_site/bin/gerrit.sh /etc/init.d/gerrit.sh
- sudo ln -snf ../init.d/gerrit.sh /etc/rc3.d/S90gerrit
+ sudo ln -snf `pwd`/review_site/bin/gerrit.sh /etc/init.d/gerrit
+ sudo ln -snf /etc/init.d/gerrit /etc/rc3.d/S90gerrit
====
To install Gerrit into an existing servlet container instead of using