Exclude LFS from the repository size limit
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
GitLab administrators that have large amount of data including git repository would like to store as much data as possible in managed object storages like S3 since they are more durable, more scalable and more affordable than block storages (or local volumes).
Currently git repository, except for LFS, is the last large data set in GitLab that still need to sit in block storage.
Those GitLab administrators, therefore, would wish their end-users store as much large data as possible in object-storage backed LFS.
Although LFS usage (ie settings) relies upon end-users and administrators cannot force them to use it,
administrators will be able to encourage the end-users to use LFS more by allowing larger capacity in LFS than block-storage backed git repository.
Proposal
UX needs to be carefully discussed considering complexity, compatibility, etc...
Below are a few of my ideas:
Option 1: Add separate LFS size limit setting alongside with the current Repository size limit setting.
- Max size in MiB,
- 0 for unlimited,
- blank for "included in the repository size limit" (compatible to current implementation)
This might be too complex.
Option 2: Add Exclude LFS from repository size limit checkbox
- LFS size will be unlimited if this is checked
This is fairly simple but LFS limit might be necessary?