You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been investigating git large-file storage solutions, and while git-fat is more generally useful, GitHub's git-lfs is a bit nicer to use. One reason is that you don't always have to explicitly tell it where your external file-storage is; if you're using GitHub Enterprise, the file-storage URL is at a predictable location relative to the upstream repo URL. This is not the case for git-fat in general, but it is probably true for most people using git-fat within an organisation.
I want to be able to put rewrite rules into ~/.gitconfig that git-fat can use to find the fat store. For example, if I run git clone ssh://git@git/repos/myproject.git on my workstation, I may know that the fat store is always going to be rsync://git@storage/git-fat/myproject and set up a rewrite rule accordingly.
Following the example of remote.<name>.fetch, such a rewrite rule might look like:
I've been investigating git large-file storage solutions, and while git-fat is more generally useful, GitHub's git-lfs is a bit nicer to use. One reason is that you don't always have to explicitly tell it where your external file-storage is; if you're using GitHub Enterprise, the file-storage URL is at a predictable location relative to the upstream repo URL. This is not the case for git-fat in general, but it is probably true for most people using git-fat within an organisation.
I want to be able to put rewrite rules into
~/.gitconfig
that git-fat can use to find the fat store. For example, if I rungit clone ssh://git@git/repos/myproject.git
on my workstation, I may know that the fat store is always going to bersync://git@storage/git-fat/myproject
and set up a rewrite rule accordingly.Following the example of
remote.<name>.fetch
, such a rewrite rule might look like:Alternatively, following the example of
url.<base>.insteadOf
, such a rewrite rule might look like:Those aren't the only two options, of course; just starting-points for discussion.
The text was updated successfully, but these errors were encountered: