GitSwarm-EE 2017.1-1 Documentation

• GitSwarm EE Git LFS Administration
  • Requirements
  • Configuration
    • Package installations
    • Installations from source
  • Known limitations

GitSwarm EE Git LFS Administration

Documentation on how to use Git LFS are under Managing large binary files with Git LFS doc.

Requirements

• Git LFS is supported in GitSwarm EE starting with version 2016.1.
• Users need to install Git LFS client version 1.0.1 and up.

Configuration

Git LFS objects can be large in size. By default, they are stored on the server GitSwarm EE is installed on.

There are two configuration options to help GitSwarm EE server administrators:

• Enabling/disabling Git LFS support

• Changing the location of LFS object storage

Package installations

In /etc/gitswarm/gitswarm.rb:

gitlab_rails['lfs_enabled'] = false

# Optionally, change the storage path location. Defaults to
# `#{gitlab_rails['shared_path']}/lfs-objects`. Which evaluates to
# `/var/opt/gitswarm/gitlab-rails/shared/lfs-objects` by default.
gitlab_rails['lfs_storage_path'] = "/mnt/storage/lfs-objects"

Installations from source

In config/gitlab.yml:

  lfs:
    enabled: false
    storage_path: /mnt/storage/lfs-objects

Known limitations

• Currently, storing GitSwarm EE Git LFS objects on a non-local storage (like S3 buckets) is not supported
• Currently, removing LFS objects from GitSwarm EE Git LFS storage is not supported
• LFS authentications via SSH is not supported for the time being
• Only compatible with the Git LFS client versions 1.1.0 or 1.0.2.