Commit 5f4300db authored by Marcia Ramos's avatar Marcia Ramos

Merge branch 'docs-update-lfs-notes' into 'master'

Clarify that LFS is enabled by default

See merge request gitlab-org/gitlab!43546
parents dc1c0982 3c46c947
...@@ -6,14 +6,16 @@ type: reference, howto ...@@ -6,14 +6,16 @@ type: reference, howto
disqus_identifier: 'https://docs.gitlab.com/ee/workflow/lfs/lfs_administration.html' disqus_identifier: 'https://docs.gitlab.com/ee/workflow/lfs/lfs_administration.html'
--- ---
# GitLab Git Large File Storage (LFS) Administration # GitLab Git Large File Storage (LFS) Administration **(CORE ONLY)**
> - Git LFS is supported in GitLab starting with version 8.2.
> - Support for object storage, such as AWS S3, was introduced in 10.0.
> - LFS is enabled in GitLab self-managed instances by default.
Documentation on how to use Git LFS are under [Managing large binary files with Git LFS doc](../../topics/git/lfs/index.md). Documentation on how to use Git LFS are under [Managing large binary files with Git LFS doc](../../topics/git/lfs/index.md).
## Requirements ## Requirements
- Git LFS is supported in GitLab starting with version 8.2.
- Support for object storage, such as AWS S3, was introduced in 10.0.
- Users need to install [Git LFS client](https://git-lfs.github.com) version 1.0.1 and up. - Users need to install [Git LFS client](https://git-lfs.github.com) version 1.0.1 and up.
## Configuration ## Configuration
...@@ -41,6 +43,8 @@ gitlab_rails['lfs_enabled'] = false ...@@ -41,6 +43,8 @@ gitlab_rails['lfs_enabled'] = false
gitlab_rails['lfs_storage_path'] = "/mnt/storage/lfs-objects" gitlab_rails['lfs_storage_path'] = "/mnt/storage/lfs-objects"
``` ```
After you update settings in `/etc/gitlab/gitlab.rb`, make sure to run [Omnibus GitLab reconfigure](../restart_gitlab.md#omnibus-gitlab-reconfigure).
### Configuration for installations from source ### Configuration for installations from source
In `config/gitlab.yml`: In `config/gitlab.yml`:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment