Phabricator supports GIT LFS for large file storage outside of the git index. Only a reference to the file is stored in git tracking the changes, the file itself is stored in phabricator's storage. WARNING: Do not store huge files (>1GB) in LFS as we have limited capacity, for data you should use your local university storage service. ## Installation * Download and install the package for your operating system: https://github.com/github/git-lfs/releases * Profit! ## Usage * In an existing git repository, initialize lfs and track a new big file, ``` git lfs install git lfs track bigfile.bin git lfs track *.png # etc ``` * Add the file to git, commit and push ``` git add bigfile.bin git add .gitattributes git commit -m "Added a bigfile using LFS" git push origin master ``` * You can also track a pattern of files, so every new file matching this pattern will be added using lfs: ```git lfs track *.png``` * Voila! ## Convert already commited files to Git LFS WARNING: This will rewrite your history and will then impact all people working on your repository * We will use BFG Repository Cleaner * Download the JAR from https://rtyley.github.io/bfg-repo-cleaner/ * Find big files extensions ``` find -type f -exec ls -lh {} \; | awk '{print $5,$9}' | sort -h ``` * Go to your git repository directory and use bfg with the extensions you found ``` java -jar bfg.jar --convert-to-git-lfs '*.{wav,pdf,avi}' ``` * Inspect your history to see the changes and clean dirty data to complete the procedure ``` git reflog expire --expire=now --all && git gc --prune=now --aggressive ``` * Push the repository back to c4science, you'll need to allow dangerous changes in the web ui before IMPORTANT: it's dangerous and will destroy your old history, have a local backup of this! ``` git push --force ```

Filesize on c4science is limited to 100MB and push size to 250MB. For special cases we support GIT LFS for large file storage outside of the git index. Only a reference to the file is stored in git tracking the changes, the file itself is stored in phabricator's storage. WARNING: Do not store huge files (>1GB) in LFS as we have limited capacity, for data you should use your local university storage service. IMPORTANT: it's dangerous and will destroy your old history, have a local backup of your repository! ## Installation * Download and install the package for your operating system: https://github.com/github/git-lfs/releases * Profit! ## Usage * In an existing git repository, initialize lfs and start tracking files, ``` git lfs install git lfs track bigfile.bin git lfs track *.png # etc ``` * Add the file to git, commit and push ``` git add bigfile.bin git add myimage.png git add .gitattributes git commit -m "Added a bigfile using LFS" git push origin master ``` * You can also track a pattern of files, so every new file matching this pattern will be added using lfs: ```git lfs track *.png``` * Voila! ## Convert already commited files to Git LFS WARNING: This will rewrite your history and will then impact all people working on your repository * We will use BFG Repository Cleaner * Download the JAR from https://rtyley.github.io/bfg-repo-cleaner/ * Find big files extensions ``` find -type f -exec ls -lh {} \; | awk '{print $5,$9}' | sort -h ``` * Go to your git repository directory and use bfg with the extensions you found ``` java -jar bfg.jar --convert-to-git-lfs '*.{wav,pdf,avi}' ``` * Inspect your history to see the changes and clean dirty data to complete the procedure ``` git reflog expire --expire=now --all && git gc --prune=now --aggressive ``` * Activate Dangereous Changes from the repository configuration: {nav Actions > Manage Repository > Basics > Actions > Allow Dangerous Changes} {F8675914} * Push the repository back to c4science ``` git push --force ``` * Deactivate Dangerous Changes (same as before)

PhabricatorFilesize on c4science is limited to 100MB and push size to 250MB. For special cases we supports GIT LFS for large file storage outside of the git index. Only a reference to the file is stored in git tracking the changes, the file itself is stored in phabricator's storage. WARNING: Do not store huge files (>1GB) in LFS as we have limited capacity, the file itself is stored in phabricator's storagefor data you should use your local university storage service. WARNING: Do not store huge files (>1GB) in LFS as we have limited capacityIMPORTANT: it's dangerous and will destroy your old history, for data you should use your local university storage service.have a local backup of your repository! ## Installation * Download and install the package for your operating system: https://github.com/github/git-lfs/releases * Profit! ## Usage * In an existing git repository, initialize lfs and track a new bistart tracking files, ``` git lfs install git lfs track bigfile.bin git lfs track *.png # etc ``` * Add the file to git, commit and push ``` git add bigfile.bin git add myimage.png git add .gitattributes git commit -m "Added a bigfile using LFS" git push origin master ``` * You can also track a pattern of files, so every new file matching this pattern will be added using lfs: ```git lfs track *.png``` * Voila! ## Convert already commited files to Git LFS WARNING: This will rewrite your history and will then impact all people working on your repository * We will use BFG Repository Cleaner * Download the JAR from https://rtyley.github.io/bfg-repo-cleaner/ * Find big files extensions ``` find -type f -exec ls -lh {} \; | awk '{print $5,$9}' | sort -h ``` * Go to your git repository directory and use bfg with the extensions you found ``` java -jar bfg.jar --convert-to-git-lfs '*.{wav,pdf,avi}' ``` * Inspect your history to see the changes and clean dirty data to complete the procedure ``` git reflog expire --expire=now --all && git gc --prune=now --aggressive ``` * Activate Dangereous Changes from the repository configuration: {nav Actions > Manage Repository > Basics > Actions > Allow Dangerous Changes} {F8675914} * Push the repository back to c4science, you'll need to allow dangerous changes in the web ui before IMPORTANT: it's dangerous and will destroy your old history, have a local backup of this! ``` git push --force ``` * Deactivate Dangerous Changes (same as before)