Skip to content

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

Open
@aleb

Description

@aleb

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions