BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
7e0e5bc3
Commit
7e0e5bc3
authored
Nov 22, 2016
by
Ben Bodenmiller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add details that Git LFS must be enabled in project
parent
3cefaca2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
3 deletions
+7
-3
manage_large_binaries_with_git_lfs.md
doc/workflow/lfs/manage_large_binaries_with_git_lfs.md
+7
-3
No files found.
doc/workflow/lfs/manage_large_binaries_with_git_lfs.md
View file @
7e0e5bc3
...
...
@@ -24,6 +24,7 @@ Documentation for GitLab instance administrators is under [LFS administration do
## Requirements
*
Git LFS is supported in GitLab starting with version 8.2
*
Git LFS must be enabled under project settings
*
[
Git LFS client
](
https://git-lfs.github.com
)
version 1.0.1 and up
## Known limitations
...
...
@@ -31,10 +32,10 @@ Documentation for GitLab instance administrators is under [LFS administration do
*
Git LFS v1 original API is not supported since it was deprecated early in LFS
development
*
When SSH is set as a remote, Git LFS objects still go through HTTPS
*
Any Git LFS request will ask for HTTPS credentials to be provided so good Git
*
Any Git LFS request will ask for HTTPS credentials to be provided so
a
good Git
credentials store is recommended
*
Git LFS always assumes HTTPS so if you have GitLab server on HTTP you will have
to add the URL to Git config manually (see
#troubleshooting
)
to add the URL to Git config manually (see
[
troubleshooting
](
#troubleshooting
)
)
>**Note**: With 8.12 GitLab added LFS support to SSH. The Git LFS communication
still goes over HTTP, but now the SSH client passes the correct credentials
...
...
@@ -95,7 +96,7 @@ available to the project anymore. Probably the object was removed from the serve
*
Local git repository is using deprecated LFS API
### Invalid status for
<url>
: 501
### Invalid status for
`<url>`
: 501
Git LFS will log the failures into a log file.
To view this log file, while in project directory:
...
...
@@ -106,6 +107,9 @@ git lfs logs last
If the status
`error 501`
is shown, it is because:
*
Git LFS is not enabled in project settings. Check your project settings and
enable Git LFS.
*
Git LFS support is not enabled on the GitLab server. Check with your GitLab
administrator why Git LFS is not enabled on the server. See
[
LFS administration documentation
](
lfs_administration.md
)
for instructions
...
...
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