| ... | ... | @@ -345,6 +345,10 @@ At present, each project has 20GB of storage space by default. As soon as 80% of |
|
|
|
|
|
|
|
Beyond this default blocking threshold, a dialogue with the DSI and the PFO team will be initiated, via a ticket to the GitLab team on the helpdesk, to assess whether the use of git (including git-lfs) generating a large use of disk space on community servers is a justified approach.
|
|
|
|
|
|
|
|
### Known limits
|
|
|
|
- LFS objects are pushed to the server despite the blocking. A separate monitoring and cleaning procedure is therefore required : unreferenced LFS files can be removed by regular tasks (set by admin) : https://gitlab.inria.fr/siteadmin/gitlab-project-size-limit/-/blob/main/proposition.md#annexe-nettoyage-des-objets-lfs
|
|
|
|
- Git LFS uses the SHA-256 hash method to generate the LFS object identifier. It is therefore only stored once on the server, even if several projects reference it. However, it is counted in the quota of each project that references it.
|
|
|
|
|
|
|
|
## How can I manage and reduce my disk space?
|
|
|
|
|
|
|
|
### When does the project disk space monitoring script run?
|
| ... | ... | |
