3

I have a Rails project, with a lot of static assets, mostly images and flash (over 500MB). The whole repository is over 1GB when including git history.

The problem is, that as a Rails developer, I don't really need to have all of those assets in the same repository, since it makes git pretty slow. I can't just drop those assets from the repository, as there are other people working on the project who might need them.

I thought about using git submodules for the assets, but that might introduce a lot of complexity.

Is there anything I can do to make working with such a bloated project more smooth? What are some best practices for working with huge projects?

Jakub Arnold
  • 85,596
  • 89
  • 230
  • 327
  • I don't see the submodule option as something adding *a lot* of complexity, if you still want everything versionned into a git repository. – greut Jan 20 '12 at 10:58

2 Answers2

2

I would really recommend storing those large static binary data in a artifact repository, like for instance Nexus.
Such a repo isn't just for Java project, or isn't just for "release" or "snapshot" releases, but also for storing any kind of binary in away which makes its administration and identification easy.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
1

Try git-annex. A more detailed answer can be found here:

https://stackoverflow.com/a/6635160/1524733

Community
  • 1
  • 1
Rog182
  • 4,829
  • 1
  • 14
  • 4