-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
server: proxy uploads in no-cache mode, allow rewriting of object bat…
…ch action href
- Loading branch information
Showing
1 changed file
with
10 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c7033ce
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saracen - I am trying to use your cache proxy. But I am getting
batch response: Repository or object not found: http://my-cache-proxy:9876/my/cache/dir/lfs/objects/batch
Check that it exists and that you have proper access to it
This is when I run git lfs pull and have
./lfscache --url -directory /my/cache/dir/lfs --http-addr=:9876 running fine -
level=info ts=2019-08-27T22:39:32.723827678Z event=listening proxy-endpoint= transport=HTTP addr=:9876
Does this work for Gitlab LFS? Is there anyway you can point out what is happening.
c7033ce
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should work fine with Gitlab LFS.
The
lfscache
command example you've provided is missing a value for the--url
argument, was this just removed because it's private? The value is usually the address to your gitlab repo, including.git/info/lfs
.If that doesn't solve it, can you please open an Issue instead of replying here?
c7033ce
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the URL because its my companies private information. But per the README I used the right URL.
I am seeing some authorization issues. Also when I run the docker command, the container starts but I do not see a public port exposed. Is that an additional step?