New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

github pages serving the reference file instead of the actual binary #1342

Open
jspillers opened this Issue Jul 1, 2016 · 12 comments

Comments

Projects
None yet
@jspillers
Copy link

jspillers commented Jul 1, 2016

I have a large file I am using git lfs to track as a part of a github.io repo. When I hit the URL to access the large file I am being served what I am assuming is the tiny reference file (134 bytes) instead of the large binary.

The file that should be the large file has the following contents:

version https://git-lfs.github.com/spec/v1
oid sha256:805400bc5ba8c96f8dff29a70c88d29c0566340b063e66f62326a1d3c3ea78ae
size 110517008

It's strange because this was just working... it wasn't until I committed a new version of the large file to the repo that I started getting this behavior. git lfs untrack + git rm and then re-adding the file appears to get it to push, but when I try to access it I get the wrong file.

The file in question is: http://www.stacktact.com/dynamic_terrain_objects_demo/Demo.unity3d

@technoweenie

This comment has been minimized.

Copy link
Member

technoweenie commented Jul 1, 2016

GitHub Pages doesn't support Git LFS. This issue isn't really the place to discuss it (this repo is for the git-lfs client), but it is something I'd like to support.

@jspillers

This comment has been minimized.

Copy link

jspillers commented Jul 1, 2016

Sorry for the noise, I will close this issue. For the future: where is the correct place to get support for git-lfs related issues that are not specific technical issues with the client?

@technoweenie

This comment has been minimized.

Copy link
Member

technoweenie commented Jul 1, 2016

Depends on the issue. Since you're asking about GitHub Pages, you'll want to hit up GitHub Support: https://github.com/contact.

That said, I'll be forwarding this issue to the team, as a way to gauge interest in new features.

HybridDog added a commit to HybridDog/hairy-avenger that referenced this issue Jul 17, 2016

see git-lfs/git-lfs#1342
M  .gitattributes
@maxnordlund

This comment has been minimized.

Copy link

maxnordlund commented Aug 9, 2016

I also would like this, and it seems like this was already mentioned in #791. On a more technical level, what would be required to allow public read access to the blob tracked by git-lfs?

I assume that that is the blocker here, after that it's just a matter of writing a jekyll plugin that transforms some hrefs.

Going with that assumption, there needs to be another API that allows for creation of unauthenticated links to the blob in question. Probably a new transfer API type would be good here.

PS. While I do understand that you want to keep GitHub out of this repo, having people contact support removes the discussion, and subsequent answers, from the public. This makes it very hard to figure/find out why it doesn't work. If there is another place where a public discussion should take place, please let us know. Anyway, just some thoughts. DS.

@oncletom

This comment has been minimized.

Copy link

oncletom commented Feb 22, 2017

I'd be interested to give some feedback or use cases about this feature – I currently include video files for a book written with Asciidoc, published on GitHub Pages as HTML pages amongst others.

Cf. oncletom/nodebook@6273c01

@justJS

This comment has been minimized.

Copy link

justJS commented Feb 23, 2017

Any updates?

@bhaskarvk

This comment has been minimized.

Copy link

bhaskarvk commented Mar 1, 2017

+1 this could really help a lot of use cases.

@harpojaeger

This comment has been minimized.

Copy link

harpojaeger commented Jul 21, 2017

Adding my +1 to the mix too!

@kyledewey

This comment has been minimized.

Copy link

kyledewey commented Sep 20, 2017

Another +1 here!

@IoriBranford

This comment has been minimized.

Copy link

IoriBranford commented Oct 2, 2017

Workaround: Commit and push LFS files first. Then link to LFS files according to this format:

https://github.com/USER/PROJ/raw/BRANCH/FILEPATH
@bryanhanson

This comment has been minimized.

Copy link

bryanhanson commented Oct 4, 2017

The workaround mentioned by @loriBranford didn't work for me, but this did:

https://github.com/USER/PROJECT/blob/gh-pages/PATH_TO_FILE?raw=true

I can't claim any great insight here, this is the path associated with the view raw link when you are in the repo looking at the file you want to access. Entering this URL in a browser generates the download file dialog box, and I was able to successfully automate a download and install in the R environment.

@royuttam

This comment has been minimized.

Copy link

royuttam commented Nov 6, 2017

Dear jspillers,
I faced the same problem. How did you overcome it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment