3 ms·

I do hardware hacking, presentations, code, pictures, and full media to reproduce what I've shared. FreeCAD files get big. And to accommodate easy printing, ST

I do hardware hacking, presentations, code, pictures, and full media to reproduce what I've shared. FreeCAD files get big. And to accommodate easy printing, STLs are also needed. KiCAD for board layout and schematics can also get larger. And remember, these also have 3d board components too. Presentations are naturally larger. Full high-rez pictures eat storage like you wouldn't believe. Code is small, thankfully. One such device I have created is hovering around 4.5GB for a full reproduction for the current snapshot. And if you do the command to pull the whole history (and not current), its around 10GB. And, I'm not sure if GL is counting the whole history, or the current? And are they pruning old after a certain date?

dnsmichi 4y ago
> And, I'm not sure if GL is counting the whole history, or the current? And are they pruning old after a certain date? GitLab stores the Git history with all data revisions as commits. To reduce the repository storage [0], older Git commits can be pruned but this would rewrite the Git history as an invasive change [1]. To store larger files, it is recommended to use Git LFS [2]. Alternatively, you can use the generic package registry to store data. [3] [0] https://docs.gitlab.com/ee/user/usage_quotas.html#manage-your-storage-usage https://docs.gitlab.com/ee/user/usage_quotas.html#manage-you... [1] https://docs.gitlab.com/ee/user/project/repository/reducing_the_repo_size_using_git.html https://docs.gitlab.com/ee/user/project/repository/reducing_... [2] https://docs.gitlab.com/ee/topics/git/lfs/ https://docs.gitlab.com/ee/topics/git/lfs/ [3] https://docs.gitlab.com/ee/user/packages/generic_packages/ https://docs.gitlab.com/ee/user/packages/generic_packages/