The following general settings are supported.įalse remote_directory The bucket name where LFS objects are stored.ĭirect_upload Set to true to enable direct upload of LFS without the need of local shared storage. GitLab-rails then uploads the file to the external object storage asynchronously.GitLab-rails stores the file in the local file storage.GitLab-workhorse notifies GitLab-rails that the upload process is complete.GitLab-workhorse uploads the file directly to the external object storage.
User pushes an lfs file to the GitLab instance.This section describes the earlier configuration format. In GitLab 13.2 and later, we recommend using the Setting up object storage supported by Fog.Changing the location of LFS object storage.There are various configuration options to help GitLab server administrators: By default, they are stored on the server Users need to install Git LFS client version 1.0.1 or later.LFS is enabled in GitLab self-managed instances by default. Known limitations GitLab Git Large File Storage (LFS) Administrationĭocumentation about how to use Git LFS are under Managing large binary files with Git LFS doc.
0 kommentar(er)
