From 1983e1597065c9f58d5dba8c617145bb0bb7401e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcia=20Ramos=20=F0=9F=9A=AB=20=28OOO=20-=20back=20on=20M?= =?UTF-8?q?ay=2021=29?= Date: Wed, 9 May 2018 16:11:28 +0000 Subject: Docs: fix duplicate titles --- doc/administration/external_database.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/administration/external_database.md (limited to 'doc/administration/external_database.md') diff --git a/doc/administration/external_database.md b/doc/administration/external_database.md new file mode 100644 index 00000000000..31199f2cdc7 --- /dev/null +++ b/doc/administration/external_database.md @@ -0,0 +1,17 @@ +# Configure GitLab using an external PostgreSQL service + +If you're hosting GitLab on a cloud provider, you can optionally use a +managed service for PostgreSQL. For example, AWS offers a managed Relational +Database Service (RDS) that runs PostgreSQL. + +Alternatively, you may opt to manage your own PostgreSQL instance or cluster +separate from the GitLab Omnibus package. + +If you use a cloud-managed service, or provide your own PostgreSQL instance: + +1. Setup PostgreSQL according to the + [database requirements document](../install/requirements.md#database). +1. Set up a `gitlab` username with a password of your choice. The `gitlab` user + needs privileges to create the `gitlabhq_production` database. +1. Configure the GitLab application servers with the appropriate details. + This step is covered in [Configuring GitLab for HA](high_availability/gitlab.md). -- cgit v1.2.1