git sizer

We have hosted the application git sizer in order to run this application in our online workstations with Wine or directly.

Quick description about git sizer:

git-sizer computes various size metrics for a local Git repository, flagging those that might cause you problems or inconvenience. Is the repository too big overall? Ideally, Git repositories should be under 1 GiB, and (without special handling) they start to get unwieldy over 5 GiB. Big repositories take a long time to clone and repack, and take a lot of disk space. Avoid storing generated files (e.g., compiler output, JAR files) in Git. It would be better to regenerate them when necessary, or store them in a package registry or even a fileserver. Avoid storing large media assets in Git. You might want to look into Git-LFS or git-annex, which allow you to version your media assets in Git while actually storing them outside of your repository. Avoid storing file archives (e.g., ZIP files, tarballs) in Git, especially if compressed. Different versions of such files don't delta well against each other, so Git can't store them efficiently.

Features:

• By default, git-sizer outputs its results in tabular format
• By default, only statistics above a minimal level of concern are reported
• git-sizer is in regular use and is still under active development
• Build and install from source
• Avoid storing log files and database dumps in Git
• Consider using Git-LFS for storing your large files

Programming Language: Go.
Categories: