Repository storage
The most important settings handle the way storage is used. Instead of using folder structures with names, you can use hashed values as directory names for projects. This way, when you're moving projects, the folder isn't moved on an OS level – the reference to the hash is changed in the database instead. Keeping a hash-based reference tree and searching is much faster than traversing a folder tree by name.
Secondly, you can specify alternate storage locations where new projects are stored. If there is more than one location, it will alternate between them in no particular order. The location that shows up in the chooser depends on what storage paths were defined in gitlab.rb (for omnibus installations) or gitlab.ym (source-based ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access