GitLab
Administration
Here are notes on running your own gitlab instance.
Terms
- unicorn - this is the web server portion of gitlab
- sidekiq - the background job processor
Basic Commands
sudo gitlab-ctl start sudo gitlab-ctl stop sudo gitlab-ctl restart
LFS
Edit the config in /etc/gitlab/gitlab.rb
and set the following:
### Git LFS gitlab_rails['lfs_enabled'] = true gitlab_rails['lfs_storage_path'] = "/var/opt/gitlab/gitlab-rails/shared/lfs-objects" # gitlab_rails['lfs_object_store_enabled'] = false # gitlab_rails['lfs_object_store_direct_upload'] = false # gitlab_rails['lfs_object_store_background_upload'] = true # gitlab_rails['lfs_object_store_proxy_download'] = false # gitlab_rails['lfs_object_store_remote_directory'] = "lfs-objects" # gitlab_rails['lfs_object_store_connection'] = { # 'provider' => 'AWS', # 'region' => 'eu-west-1', # 'aws_access_key_id' => 'AWS_ACCESS_KEY_ID', # 'aws_secret_access_key' => 'AWS_SECRET_ACCESS_KEY', # # # The below options configure an S3 compatible host instead of AWS # # 'aws_signature_version' => 4 # For creation of signed URLs. Set to 2 if provider does not support v4. # # 'endpoint' => 'https://s3.amazonaws.com' # default: nil - Useful for S3 compliant services such as DigitalOcean Spaces # # 'host' => 's3.amazonaws.com', # # 'path_style' => false # Use 'host/bucket_name/object' instead of 'bucket_name.host/object' # }
- Notes
- If you change the LFS directory, you should run
sudo gitlab-ctl reconfigure
- The LFS directory should be
700
andgit:root
. - Parent directories need to have permissions
775
withgit
in the group or owned by usergit
. - See https://docs.gitlab.com/omnibus/settings/configuration.html#disable-storage-directories-management for more details.
- The LFS directory should be