It can be simply put up this way:
If you don’t need to apply on the go transformations, or use API or something to access the files, that is all you need to do it link to them on your website, don’t use LFS.
These 2 threads might give more info:
Howdy!
The main reasons I recommend people not use it is:
that folks who are not git-savvy try to use it and get stuck in can’t-even-push-my-repo configurations. (the git config is a bit intense, but you’ve clearly done your reading and if you feel comfortable using git LFS anyway, this is probably not you :))
that the benefits for folks who don’t use the transformations are slim to none. You can use LFS on your own without the service, to speed up clones here and locally.
in case you don’t …
I suspect you will have a very hard time uploading that much data into less than a series of 20 sites. Our CDN is optimized for much smaller files, and also for much smaller deploys.
However, we charge for transfer, so anyting you can fit in, that is referred to by your html, is not against our ToS. This is in contrast to say uploading something that is used just by e.g. a game that runs on people’s PC’s and pulls art from our servers via API, rather than in a browser.
TL;DR feel free to giv…
1 Like