3 ms·
For me it's just that Git LFS defaults to a server. I'm rewriting it largely because i loathe Git-LFS needing to hit some HTTP server. Running one locally becau
by unshavedyak 4y ago
For me it's just that Git LFS defaults to a server. I'm rewriting it largely because i loathe Git-LFS needing to hit some HTTP server. Running one locally because they defaulted to a Github Webserver mindset frustrates me.
- throwaway290 4y agoPersonally if files are large I prefer to store all of them and the entire history of their changes somewhere else, so a server makes sense to me...
- unshavedyak 4y agoYea, i just don't want to be forced to. Ie to me storing them in another folder, a network filesystem, some SSH filesystem, a dumb KV store like S3, etc are all viable storage locations to it. So that's what i'm writing because i'm just picky, i guess heh.
- throwaway290 4y agoThe spec says pointer is just an URL so it could probably be a file:... or s3:... URL if you have the right resolver logic