All geek questions in one place

Are there tools for managing large binaries in git on Windows?

I am already familiar with the answers to a general question: how to manage large binaries in git (or a large number of files). And I looked at git-annex , bup and git -media. None of them require very good access for a Windows user.

Are there any programs that work well on Windows?

To add context, I try to control versions of the system deployment bits: OS images, drivers, third-party installers, first-person installers (our applications). I need to have everything in a cohesive bundle (tags). And to be able to get the whole package for any of our active releases.

+6
source share
2 answers

I don’t know what I know, and as you know, large binaries are not compatible with:

  • VCS (since it makes no sense to distinguish between them or their merger)
  • DVCS (where the distributed repo is for cloning, which is quickly cumbersome with the expected repo)

The only remaining solution (actually OS agnostics) is an external artifact repository (for example, Nexus one) to save these binaries.

OP Anthony Mastrean adds what he needs:

the version controls the system deployment bits: OS images, drivers, third-party installers, first-party installers (our applications).
I need to have everything in a cohesive bundle (tags). And be able to get the whole kit for any of our active releases

This will be a mix:

  • development requirements (versions that mean branching and comparing versions)
  • with deployment requirements (getting all the correct labels for deployment and launch)

Everything that has not been developed (i.e., something built or already existing) should be outside VCS (with the exception of very small resources, such as icons that do not change much).

Usually you use the version of "release", which contains all the additional information (checksums, path to other references, ...) for deploying the script to work, choosing the right artifacts.

+3
source

It is not possible to manage large binaries in GIT or any other version control system. The consensus is that for this you need digital asset management systems. Digital assets are things like photos, sound clips, videos, etc.

There are several open source DAM packages, and this page has an overview of all the major http://www.opensourcedigitalassetmanagement.org/

If you don't need support for version control, many people create quick solutions using something like MongoDB for storage.

+2
source

Source: https://habr.com/ru/post/894880/

More articles:


All Articles