Skip to content
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

lfs objects are not mirrored #98

Open
agonycoder opened this issue Jan 11, 2017 · 6 comments
Open

lfs objects are not mirrored #98

agonycoder opened this issue Jan 11, 2017 · 6 comments

Comments

@agonycoder
Copy link

I believe it wouldn't be very hard to add this although gitlab mirror seems to have a long discussion about it as well. Maybe the 90% success simplistic case would suffice?

@samrocketman
Copy link
Owner

Can you elaborate on how one would mirror git lfs? I'm not to familiar with it. PRs are also welcome.

@samrocketman
Copy link
Owner

samrocketman commented Feb 2, 2017

Also, I have no idea what the 90% success simplistic case is referencing.

@nicholas-itpedia
Copy link

@samrocketman I think 90% success simplistic case means a simple solutions will make 90% happy and the complicated solution to get that last 10%.

@samrocketman
Copy link
Owner

samrocketman commented Feb 10, 2017

@nicholas-itpedia I don't use git lfs and don't know what the "90% case" is technically (i.e. what commands are the 90% case?). If you have links to how others are mirroring git lfs objects I would be happy to take a look.

For instance @agonycoder mentions GitLab has a long discussion about it. Could I have a link to that discussion for reading?

@wrightsg
Copy link

I stumbled accross this issue while trying out gitlab-mirrors.

I implemented a quick and dirty attempt at using Git LFS in the provided scripts (see https://github.com/wrightsg/gitlab-mirrors/tree/git-lfs-support) based on the instructions in the link provided by @wangzw

I have tested initial mirrorring using the add_mirror.sh script and updating using the git-mirrors.sh script.

I am not really a Git LFS expert and these changes most likely to not cover all cases. Maybe someone with more experience can weigh in.

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

No branches or pull requests

5 participants