summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLee Matos <lee@gitlab.com>2019-05-17 18:21:51 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2019-05-17 18:21:51 +0000
commitc5935469e1bb4370d76532ddce84f8e37a9d14a1 (patch)
treedda1704ad6068571883567928412e5e541f1cddb
parent1c19a89a57e93b51fca1fbef3cc8f687463cebb2 (diff)
downloadgitlab-ce-c5935469e1bb4370d76532ddce84f8e37a9d14a1.tar.gz
Update manage_large_binaries_with_git_lfs.md to clarify LFS external storage caveats
-rw-r--r--doc/workflow/lfs/manage_large_binaries_with_git_lfs.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md b/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md
index da0243705aa..202f2e39975 100644
--- a/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md
+++ b/doc/workflow/lfs/manage_large_binaries_with_git_lfs.md
@@ -250,6 +250,7 @@ If you are storing LFS files outside of GitLab you can disable LFS on the projec
It is possible to host LFS objects externally by setting a custom LFS url with `git config -f .lfsconfig lfs.url https://example.com/<project>.git/info/lfs`.
-Because GitLab verifies the existence of objects referenced by LFS pointers, push will fail when LFS is enabled for the project.
+You might choose to do this if you are using an appliance like a Sonatype Nexus to store LFS data. If you choose to use an external LFS store,
+GitLab will not be able to verify LFS objects which means that pushes will fail if you have GitLab LFS support enabled.
-LFS can be disabled from the [Project settings](../../user/project/settings/index.md).
+To stop push failure, LFS support can be disabled in the [Project settings](../../user/project/settings/index.md). This means you will lose GitLab LFS value-adds (Verifying LFS objects, UI integration for LFS).