2019-05-27 11:49:21 +00:00
|
|
|
---
|
|
|
|
type: reference
|
|
|
|
---
|
|
|
|
|
2019-05-05 14:17:38 +00:00
|
|
|
# Account and limit settings
|
|
|
|
|
|
|
|
## Repository size limit **[STARTER]**
|
|
|
|
|
2019-05-27 11:49:21 +00:00
|
|
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/740) in [GitLab Enterprise Edition 8.12](https://about.gitlab.com/2016/09/22/gitlab-8-12-released/#limit-project-size-ee).
|
|
|
|
> Available in [GitLab Starter](https://about.gitlab.com/pricing/).
|
2019-05-05 14:17:38 +00:00
|
|
|
|
|
|
|
Repositories within your GitLab instance can grow quickly, especially if you are
|
2019-05-27 11:49:21 +00:00
|
|
|
using LFS. Their size can grow exponentially, rapidly consuming available storage.
|
2019-05-05 14:17:38 +00:00
|
|
|
|
2019-05-27 11:49:21 +00:00
|
|
|
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.
|
2019-05-05 14:17:38 +00:00
|
|
|
|
2019-05-27 11:49:21 +00:00
|
|
|
There are numerous use cases where you might set up a limit for repository size.
|
2019-05-05 14:17:38 +00:00
|
|
|
For instance, consider the following workflow:
|
|
|
|
|
2019-05-27 11:49:21 +00:00
|
|
|
1. Your team develops apps which require large files to be stored in
|
2019-05-05 14:17:38 +00:00
|
|
|
the application repository.
|
2019-05-27 11:49:21 +00:00
|
|
|
1. Although you have enabled [Git LFS](../../../workflow/lfs/manage_large_binaries_with_git_lfs.md#git-lfs)
|
2019-05-05 14:17:38 +00:00
|
|
|
to your project, your storage has grown significantly.
|
2019-05-27 11:49:21 +00:00
|
|
|
1. Before you exceed available storage, you set up a limit of 10 GB
|
2019-05-05 14:17:38 +00:00
|
|
|
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.
|
|
|
|
- A group's settings.
|
|
|
|
- The **Size limit per repository (MB)** field in the **Account and limit** section of a GitLab instance's
|
|
|
|
settings by navigating to either:
|
|
|
|
- **Admin Area > Settings > General**.
|
|
|
|
- The path `/admin/application_settings`.
|
|
|
|
|
|
|
|
The very first push of a new project cannot be checked for size as of now, so
|
|
|
|
the first push will allow you to upload more than the limit dictates, but every
|
|
|
|
subsequent push will be denied. LFS objects, however, can be checked on first
|
|
|
|
push and **will** be rejected if the sum of their sizes exceeds the maximum
|
|
|
|
allowed repository size.
|
|
|
|
|
2019-05-27 11:49:21 +00:00
|
|
|
For details on manually purging files, see [reducing the repository size using Git](../../project/repository/reducing_the_repo_size_using_git.md).
|
|
|
|
|
|
|
|
NOTE: **Note:**
|
|
|
|
For GitLab.com, the repository size limit is 10 GB.
|
|
|
|
|
|
|
|
<!-- ## Troubleshooting
|
2019-05-05 14:17:38 +00:00
|
|
|
|
2019-05-27 11:49:21 +00:00
|
|
|
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
|
|
|
one might have when setting this up, or when something is changed, or on upgrading, it's
|
|
|
|
important to describe those, too. Think of things that may go wrong and include them here.
|
|
|
|
This is important to minimize requests for support, and to avoid doc comments with
|
|
|
|
questions that you know someone might ask.
|
2019-05-05 14:17:38 +00:00
|
|
|
|
2019-05-27 11:49:21 +00:00
|
|
|
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
|
|
|
|
If you have none to add when creating a doc, leave this section in place
|
|
|
|
but commented out to help encourage others to add to it in the future. -->
|