Stories
Slash Boxes
Comments

SoylentNews is people

posted by LaminatorX on Thursday April 09 2015, @07:24PM   Printer-friendly
from the GitHub-Git-on-Hub dept.

GitHub is announcing that is will soon support the open source extension Git LFS (Large File System) on every repository they host.

This extension allows the replacement of large files (audio samples, images, textures models, various assets...) by references pointing to a remote server, allowing you to store huge files in your repository. While GitHub is only now implementing it as part of its service, it can be used without GitHub as of now.

This system could easily benefit organizations and projects relying on a heavy quantity of assets.

See the official announcement here on the GitHub blog.

Do you use GitHub for your work? How do you think this could be implemented in your organization and projects? I know this will end up replacing the complex workflow I have put in place in my company, based on on a intricate system of submodules.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by c0lo on Thursday April 09 2015, @09:07PM

    by c0lo (156) Subscriber Badge on Thursday April 09 2015, @09:07PM (#168497) Journal
    If the workflow in itself is complex, why do you think relying on GitHit will simplify it?
    (did the complexity crept in because of limited storage resources or is the production workflow inherently complex?)
    --
    https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 3, Informative) by Marneus68 on Friday April 10 2015, @11:06AM

    by Marneus68 (3572) on Friday April 10 2015, @11:06AM (#168696) Homepage

    >If the workflow in itself is complex, why do you think relying on GitHit will simplify it?
    GitHub doesn't simplify anything, Git LFS could.

    >(did the complexity crept in because of limited storage resources or is the production workflow inherently complex?)
    The complexity is inherent to the type of project we make (we have our own framework with needs to be tracked, plugins for the engine with their own codebase but where we only need to have the binaries in the end project, the business specific code using a specific version of our internal framework, and then you have the assets). Building the final product isn't hard, creating a versionning scheme that prevents storing duplicates of shared resources is what makes the whole process complex.