Configuring Git Large File Storage for your enterprise

About Git Large File Storage

Git Large File Storage (Git LFS) 是 Git 的开源扩展，使您能够像处理其他文本文件一� �处理大文件。 You can use Git Large File Storage with a single repository, all of your personal or organization repositories, or with every repository in your enterprise. Before you can enable Git LFS for specific repositories or organizations, you need to enable Git LFS for your enterprise.

By default, the Git Large File Storage client stores large assets on the same server that hosts the Git repository. When Git LFS is enabled on your GitHub Enterprise Server instance, large assets are stored on the data partition in /data/user/storage.

如果在企业或仓库上禁用了 Git LFS，则用户� 法将 Git LFS 资产推送到 GitHub Enterprise Server 。

For more information, see "About Git Large File Storage", "Versioning large files," and the Git Large File Storage project site.

Configuring Git Large File Storage for your enterprise

1. 在 GitHub Enterprise Server 的右上角，单击� 的个人资料照片，然后单击“企业设置”。

2. 在企业边� �中，单击 “策略”。

3. 在 “策略” 下，单击“选项” 。

4. Under "Git LFS access", use the drop-down menu, and click Enabled or Disabled.

Configuring Git Large File Storage for an individual repository

1. 从 GitHub Enterprise Server 上的管理帐户任意页面的右上角，单击 。

   

2. 如果� 尚未在“站点管理员”页上，请在左上角单击“站点管理员”。

   

3. 在搜索字段中，键入存储库的名称，然后单击“搜索”。

4. 在搜索结果中，单击仓库名称。

5. 在页面的右上角，单击 “管理员”。

6. 在左侧� �中，单击“管理员”。

7. 在“Git LFS”下，单击“启用”或“禁用” 。

Configuring Git Large File Storage for every repository owned by a user account or organization

1. 从 GitHub Enterprise Server 上的管理帐户任意页面的右上角，单击 。

   

2. 如果� 尚未在“站点管理员”页上，请在左上角单击“站点管理员”。

   

3. 在搜索字段中，键入用户或组织的名称，然后单击“搜索”。

4. 在搜索结果中，单击用户或组织的名称。

5. 在页面的右上角，单击 “管理员”。

6. 在左侧� �中，单击“管理员”。

7. 在“Git LFS”下，单击“启用”或“禁用” 。

Configuring Git Large File Storage to use a third party server

By default, the Git Large File Storage client stores large assets on the same server that hosts the Git repository. When Git LFS is enabled on your GitHub Enterprise Server instance, large assets are stored on the data partition in /data/user/storage.

如果在企业或仓库上禁用了 Git LFS，则用户� 法将 Git LFS 资产推送到 GitHub Enterprise Server 。

1. Disable Git LFS on your GitHub Enterprise Server instance. For more information, see "Configuring Git Large File Storage for your enterprise."

2. Create a Git LFS configuration file that points to the third party server.

   # Show default configuration
   $ git lfs env
   > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
   > git version 2.7.4 (Apple Git-66)
   � 
   > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic)
   � 
   # Create .lfsconfig that points to third party server.
   $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo
   $ git lfs env
   > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
   > git version 2.7.4 (Apple Git-66)
   � 
   > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none)
   � 
   # Show the contents of .lfsconfig
   $ cat .lfsconfig
   [remote "origin"]
   lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo

3. To keep the same Git LFS configuration for each user, commit a custom .lfsconfig file to the repository.

   $ git add .lfsconfig
   $ git commit -m "Adding LFS config file"

4. Migrate any existing Git LFS assets. For more information, see "Migrating to a different Git Large File Storage server."

Migrating to a different Git Large File Storage server

Before migrating to a different Git Large File Storage server, you must configure Git LFS to use a third party server. For more information, see "Configuring Git Large File Storage to use a third party server."

1. Configure the repository with a second remote.

   $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo
   � 
   $ git lfs env
   > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
   > git version 2.7.4 (Apple Git-66)
   � 
   > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic)
   > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none)

2. Fetch all objects from the old remote.

   $ git lfs fetch origin --all
   > Scanning for all objects ever referenced...
   > ✔ 16 objects found
   > Fetching objects...
   > Git LFS: (16 of 16 files) 48.71 MB / 48.85 MB

3. Push all objects to the new remote.

   $ git lfs push NEW-REMOTE --all
   > Scanning for all objects ever referenced...
   > ✔ 16 objects found
   > Pushing objects...
   > Git LFS: (16 of 16 files) 48.00 MB / 48.85 MB, 879.10 KB skipped

Further reading

• Git Large File Storage project site