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

"no need for secondary storage systems" true only for compatible git service providers #22

Open
aleb opened this issue Jul 19, 2017 · 1 comment

Comments

@aleb
Copy link

aleb commented Jul 19, 2017

The "Same Git workflow" says:

Work like you always do on Git—no need for additional commands, secondary storage systems, or toolsets.

The statement is indeed true when using GitHub, Atlassian, GitLab, etc. but if you run your own official git server, it cannot be used as is by git-lfs, so a "secondary storage system" which is a git-lfs server is actually needed. It would be useful to mention this distinction.

Related: Since there is no official git-lfs server implementation yet, one has to dig through implementations to find one which can actually be run and supports the latest git-lfs features. I still did not find any appealing implementation. The page could set better the path/expectations for people with a standard git server.

@ttaylorr
Copy link
Contributor

Hi @aleb, thanks for opening this.

it cannot be used as is by git-lfs, so a "secondary storage system" which is a git-lfs server is actually needed. It would be useful to mention this distinction.

Good point! Do you think you could open a PR with some suggested phrasing?

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

No branches or pull requests

3 participants
@ttaylorr @aleb and others