What's the best way to version control graphical assets on Windows?

I’m a web developer / designer, and I want to be able to version control graphic files (Photoshop / Fireworks / Illustrator / Stock Photos / etc).

This would normally be fine but some of the files I have tip the scales at around 800MB, which TortoiseHG chokes on. I currently have a server I put all my files on so all my computers can access (it’s my work computer and I have some flexibility as to installing some linux packages).

  • How much space can your BitBucket account have?
  • Mirroring repository via fileserver
  • Convert multiple hg repositories to single git repository with multiple branches
  • Version Control: Managing Common Component Source
  • Why is checking in files called a 'commit'?
  • merge-base analog for Mercurial and bzr (to find common ancestors as possible for a merge)?
  • Any advice on the best way to go about this would be appreciated.

  • Git or Subversion for a TFS user
  • On Windows, can we put different folders in 1 Git or Mercurial (hg) repository?
  • AnkhSVN Commits Are Very Slow
  • Deployment of Continuous Integration Infrastructure
  • 'svn add' interactive
  • How to ignore files/folders using SVN in PHPstorm
  • 2 Solutions collect form web for “What's the best way to version control graphical assets on Windows?”

    Unless those graphic files changes every day, a better way to store them would be to:

    • avoid VCS (CVCS like SVN or DVCS like Git or Mercurial): those are made to keep the history of elements, with the possibility to compare with older versions.
      You rarely need that with graphic files.

    • use a generic repository (i.e. a shared directory with naming convention of tagging feature, not one with branching and merging like a VCS).
      I generally use a maven-based repo like Nexus.
      I then store in the VCS a text file which will contain the exact label of the artifacts (in your case the “set of graphic files”) referenced in the Nexus repository. That text file also include a MD5 checksum.

    That solution allows your repositories (both the VCS one and the artifact one) to scala nicely together.

    I’m not sure whether they’ll suit your needs but you can find a couple of suggestions at http://sixrevisions.com/project-management/the-ultimate-guide-to-version-control-for-designers/

    Git Baby is a git and github fan, let's start git clone.