Account and limit settings
Max attachment size
You can change the maximum file size for attachments in comments and replies in GitLab.
Navigate to Admin Area (wrench icon) > Settings > General, then expand Account and Limit.
From here, you can increase or decrease by changing the value in Maximum attachment size (MB)
.
Repository size limit
Introduced in GitLab Enterprise Edition 8.12. Available in GitLab Starter.
Repositories within your GitLab instance can grow quickly, especially if you are using LFS. Their size can grow exponentially, rapidly consuming available storage.
To avoid this from happening, you can set a hard limit for your repositories’ size. This limit can be set globally, per group, or per project, with per project limits taking the highest priority.
There are numerous use cases where you might set up a limit for repository size. For instance, consider the following workflow:
- Your team develops apps which require large files to be stored in the application repository.
- Although you have enabled Git LFS to your project, your storage has grown significantly.
- Before you exceed available storage, you set up a limit of 10 GB per repository.
How it works
Only a GitLab administrator can set those limits. Setting the limit to 0
means
there are no restrictions.
These settings can be found within:
- Each project’s settings:
- From the Project’s homepage, navigate to Settings > General.
- Fill in the Repository size limit (MB) field in the Naming, topics, avatar section.
- Click Save changes.
- Each group’s settings:
- From the Group’s homepage, navigate to Settings > General.
- Fill in the Repository size limit (MB) field in the Naming, visibility section.
- Click Save changes.
- GitLab’s global settings:
- From the Dashboard, navigate to Admin Area > Settings > General.
- Expand the Account and limit section.
- Fill in the Size limit per repository (MB) field.
- Click Save changes.
The first push of a new project, including LFS objects, will be checked for size and will be rejected if the sum of their sizes exceeds the maximum allowed repository size.
Note: The repository size limit includes repository files and LFS, and does not include artifacts.
For details on manually purging files, see reducing the repository size using Git.
Troubleshooting
413 Request Entity Too Large
If you are attaching a file to a comment or reply in GitLab and receive the 413 Request Entity Too Large
error, it is likely caused by having a max attachment size
larger than what the web server is configured to allow.
If you wanted to increase the max attachment size to 200m in a GitLab
Omnibus install, for example, you might need to
add the line below to /etc/gitlab/gitlab.rb
before increasing the max attachment size:
nginx['client_max_body_size'] = "200m"
Limiting lifetime of personal access tokens
Introduced in GitLab Ultimate 12.6.
Users can optionally specify an expiration date for personal access tokens. This expiration date is not a requirement, and can be set to any arbitrary date.
Since personal access tokens are the only token needed for programmatic access to GitLab, organizations with security requirements may want to enforce more protection to require regular rotation of these tokens.
Setting a limit
Only a GitLab administrator can set a limit. Leaving it empty means there are no restrictions.
To set a limit on how long personal access tokens are valid:
- Navigate to Admin Area > Settings > General.
- Expand the Account and limit section.
- Fill in the Maximun allowable lifetime for personal access tokens (days) field.
- Click Save changes.
Once a lifetime for personal access tokens is set, GitLab will:
- Apply the lifetime for new personal access tokens, and require users to set an expiration date and a date no later than the allowed lifetime.
- After three hours, revoke old tokens with no expiration date or with a lifetime longer than the allowed lifetime. Three hours is given to allow administrators to change the allowed lifetime, or remove it, before revocation takes place.
Help and feedback
If there's something you don't like about this feature
To propose functionality that GitLab does not yet offer
To further help GitLab in shaping new features
If you didn't find what you were looking for
If you want help with something very specific to your use case, and can use some community support
POST ON GITLAB FORUM
If you have problems setting up or using this feature (depending on your GitLab subscription)
REQUEST SUPPORT
To view all GitLab tiers and features or to upgrade
If you want to try all features available in GitLab.com
If you want to try all features available in GitLab self-managed
If you spot an error or a need for improvement and would like to fix it yourself in a merge request
EDIT THIS PAGE
If you would like to suggest an improvement to this doc
If you want to give quick and simple feedback on this doc