jedbrown / git-fat

Simple way to handle fat files without committing them to git, supports synchronization using rsync
BSD 2-Clause "Simplified" License
622 stars 136 forks source link

git-fat and offline repositories #91

Open chirag12345678 opened 5 years ago

chirag12345678 commented 5 years ago

Hello all,

This isn't really an issue, but just a means to get some clarity and guidance. I am trying to ensure that a repo is correctly replicated on another site (and none are available outside their respective intranets).. I have a machine with a git repo and using git-fat for executables/binaries. I'd like to be able to somehow git-bundle and copy contents to the client site for version control... I'd like to understand how to do this correctly and still be able to use git-fat (or is git-fat not the right approach) for my application... site1: git init x cd x ... git commit -m "something" git fat push git-bundle repo and put it on sftp

site2 (not available directly through internet): retrieve from sftp and un-bundle now how do I setup the git-fat such that the client site clones point to a location that is common to all for the [rsync] section of the fat files (to pull from).. these clones should literally be read-only and not have any commit privileges... hopefully I am describing my problem accurately... let me know if this needs more clarity... also, i'd like the commit history to be maintained (hence the git-bundle) between the two repos... thanks.