diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-20 17:34:42 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-20 17:34:42 +0300 |
commit | 9f46488805e86b1bc341ea1620b866016c2ce5ed (patch) | |
tree | f9748c7e287041e37d6da49e0a29c9511dc34768 /doc/administration/object_storage.md | |
parent | dfc92d081ea0332d69c8aca2f0e745cb48ae5e6d (diff) |
Add latest changes from gitlab-org/gitlab@13-0-stable-ee
Diffstat (limited to 'doc/administration/object_storage.md')
-rw-r--r-- | doc/administration/object_storage.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/administration/object_storage.md b/doc/administration/object_storage.md index 1b0c7f8a907..c4f9b672923 100644 --- a/doc/administration/object_storage.md +++ b/doc/administration/object_storage.md @@ -5,7 +5,7 @@ type: reference # Object Storage GitLab supports using an object storage service for holding numerous types of data. -In a high availability setup, it's recommended over [NFS](high_availability/nfs.md) and +It's recommended over NFS and in general it's better in larger setups as object storage is typically much more performant, reliable, and scalable. @@ -37,8 +37,8 @@ For configuring GitLab to use Object Storage refer to the following guides: ### Other alternatives to filesystem storage -If you're working to [scale out](scaling/index.md) your GitLab implementation, -or add [fault tolerance and redundancy](high_availability/README.md) you may be +If you're working to [scale out](reference_architectures/index.md) your GitLab implementation, +or add fault tolerance and redundancy, you may be looking at removing dependencies on block or network filesystems. See the following guides and [note that Pages requires disk storage](#gitlab-pages-requires-nfs): @@ -77,7 +77,7 @@ with the Fog library that GitLab uses. Symptoms include: ### GitLab Pages requires NFS -If you're working to add more GitLab servers for [scaling or fault tolerance](scaling/index.md) +If you're working to add more GitLab servers for [scaling or fault tolerance](reference_architectures/index.md) and one of your requirements is [GitLab Pages](../user/project/pages/index.md) this currently requires NFS. There is [work in progress](https://gitlab.com/gitlab-org/gitlab-pages/issues/196) to remove this dependency. In the future, GitLab Pages may use @@ -98,9 +98,9 @@ object storage back end, like when Git clients request large files via LFS or wh downloading CI artifacts and logs. When the files are stored on local block storage or NFS, GitLab has to act as a proxy. -This is not the default behaviour with object storage. +This is not the default behavior with object storage. -The `proxy_download` setting controls this behaviour: the default is generally `false`. +The `proxy_download` setting controls this behavior: the default is generally `false`. Verify this in the documentation for each use case. Set it to `true` so that GitLab proxies the files. |