Below you will find the configuration options required to enable it. Git-annex is disabled by default in GitLab. If you need the large binary, you can sync it from the GitLab server over rsync, a very fast file copying tool. You check-in only a symlink that contains the SHA-1 of the large binary. Git-annex allows managing large binaries with Git without checking the contents into Git. This problem is solved in GitLab Enterprise Edition by integrating the git-annex application. This results in using outdated files, not having a complete history and increases the risk of losing work.

As a workaround, people keep artwork-in-progress in a Dropbox folder and only check in the final result. Videos, photos, audio, compiled binaries and many other types of files are too large. Not being able to version control large binaries is a big problem for many larger organizations. Although GitLab has no limit (some repositories in GitLab are over 50GB!), we subscribe to the advice to keep repositories as small as you can. The general recommendation is to not have Git repositories larger than 1GB to preserve performance. The biggest limitation of Git, compared to some older centralized version control systems, has been the maximum size of the repositories. Read through the migration guide from git-annex to git-lfs. It will be completely removed in GitLab 9.0 (2). Warning: GitLab is deprecating git-annex support from GitLab 8.17 (2) on. git-annex-shell: Not a git-annex or gcrypt repository.Configuration for installations from source.

Using git annex with gitlab