Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
80d90873
Commit
80d90873
authored
Oct 03, 2019
by
Max Woolf
Committed by
Evan Read
Oct 03, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
ADD: Documentation around using external production PSQL providers in Auto DevOps pipelines
parent
ba756701
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
29 additions
and
0 deletions
+29
-0
doc/topics/autodevops/img/disable_postgres.png
doc/topics/autodevops/img/disable_postgres.png
+0
-0
doc/topics/autodevops/index.md
doc/topics/autodevops/index.md
+29
-0
No files found.
doc/topics/autodevops/img/disable_postgres.png
0 → 100644
View file @
80d90873
9.77 KB
doc/topics/autodevops/index.md
View file @
80d90873
...
@@ -847,6 +847,35 @@ the database are preconfigured, but can be customized by setting the associated
...
@@ -847,6 +847,35 @@ the database are preconfigured, but can be customized by setting the associated
postgres://user:password@postgres-host:postgres-port/postgres-database
postgres://user:password@postgres-host:postgres-port/postgres-database
```
```
#### Using external PostgreSQL database providers
While Auto DevOps provides out-of-the-box support for a PostgreSQL container for
production environments, for some use-cases it may not be sufficiently secure or
resilient and you may wish to use an external managed provider for PostgreSQL.
For example, AWS Relational Database Service.
You will need to define environment-scoped variables for
`POSTGRES_ENABLED`
and
`DATABASE_URL`
in your project's CI/CD settings.
To achieve this:
1.
Disable the built-in PostgreSQL installation for the required environments using
scoped
[
environment variables
](
../../ci/environments.md#scoping-environments-with-specs
)
.
For this use case, it's likely that only
`production`
will need to be added to this
list as the builtin PostgreSQL setup for Review Apps and staging will be sufficient
as a high availability setup is not required.
!
[
Auto Metrics
](
img/disable_postgres.png
)
1.
Define the
`DATABASE_URL`
CI variable as a scoped environment variable that will be
available to your application. This should be a URL in the following format:
```
yaml
postgres://user:password@postgres-host:postgres-port/postgres-database
```
You will need to ensure that your Kubernetes cluster has network access to wherever
PostgreSQL is hosted.
### Environment variables
### Environment variables
The following variables can be used for setting up the Auto DevOps domain,
The following variables can be used for setting up the Auto DevOps domain,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment