TerribleDev/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct git -> Git

Browse Source
This commit is contained in:
Ross McDonald
2018-04-18 16:53:58 -05:00
parent 732f29be9f
commit 5b7d44bfbc
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
articles/enterprise/components/gitlab.md
View File

@@ -13,14 +13,14 @@ addition to storing files, GitLab is responsible for:
Packaged within the GitLab CE is an installation of PostgreSQL and Redis. These
two sub-components can be broken out into external services if your organization
is already familiar with running these (or similar) services. You may also break
out these services if you plan on using a managed hosting solution, for example
out these services if you plan on using a managed hosting solution, for example,
Amazon RDS (for PostgreSQL) or Amazon ElastiCache (for Redis).
> ### Requirements
>
> #### Storage
>
> GitLab requires persistent storage in order to store Stoplight file data (in git), and optionally PostgreSQL data (when using the omnibus package).
> GitLab requires persistent storage in order to store Stoplight file data (in Git), and optionally PostgreSQL data (when using the omnibus package).
>
> #### Networking
>

4
articles/enterprise/maintenance/backups.md
View File

@@ -4,9 +4,9 @@ Backups are a critical component to ensuring the health of the Stoplight
platform. When creating a backup and restore strategy for your on-premise
installation, be sure to include the following locations:
* The **GitLab data directory**, which includes the raw filesystem data backing each projects git repository.
* The **GitLab data directory**, which includes the raw filesystem data backing each projects Git repository.
* The **GitLab configuration directory**, which includes randomly-generated secrets and keys necessary for securing the GitLab runtime.
* The **GitLab PostgreSQL database**, which includes user, group, permissions, and other relational data not included in the git repositories.
* The **GitLab PostgreSQL database**, which includes user, group, permissions, and other relational data not included in the Git repositories.
* The **Pubs data directory**, which includes published hubs and their corresponding configurations.
Backing up all locations above will ensure you can properly restore a Stoplight