Hi. I tried to use the netlify git-lfs service for my hugo website project, but it turns out that I need to know image size (width and height in pixel) when generating site, (because I’m using photoswipe to enlarge image full size and full screen). And this information is not available to hugo when using netlify git lfs. This problem is documented, in the limitations of git lfs with netlify.
Files tracked with Large Media are uploaded directly to the Netlify Large Media storage service on push, completely bypassing the site build. This saves build time, but also means that the files are not available to tools that process asset files during the build, such as Hugo’s image processing. […] Depending on your needs, you may be able to replace this functionality with Netlify’s image transformation service.
But it turns out image transformation service doesn’t give a way to output original image width and height in pixel.
So after my intent to use this netlify git-lfs service, I gave up and found another solution (sadly, because my hugo build time on netlify dropped down drastically from 30s-40s to only 1s when I was using netlify large media server).
I hosted my website sources on gitlab, I think everything is ready there, I have my repository pushed, git lfs enabled and all my lfs files uploadeds to gitlab lfs server. No I need to
change the repo that netlify use for my website (currently it uses a github repo, I’d like to switch to gitlab)
Because Netlify Large Media and Git LFS change the way your files are saved, disabling Large Media requires assistance from Netlify Support. To request this assistance, please make a new topic in our Support Forums
I’m writting here to request this assistance. Or maybe it will be simpler to delete my website and recreate it from gitlab ?
Thanks for letting us know you want to uninstall the Large Media add-on for your site. Would you please confirm you have read the following Support Guide?
If you have read that, please confirm you have backups of all files and let us know which site to remove Large Media from. To identify the site, you can send us the site subdomain, API ID (the id not the key), or a link to the site (whichever you prefer).
Once we know which site, we’ll reply soon to confirm the add-on has been uninstalled.
Please let us know if there are any questions and, if not, please tell us the site to do this for.
Thank you for your reply. Yes I have read the guide, I’m absolutely certain I have local backups off all required files. You can remove Large Media from www.pauavo.fr.
Hi, @pau-a-velo. We have removed the Large Media add-on from the site now.
Would you please push the commit removing .lfsconfig to the upstream repository? This will trigger a new build.
Please keep in mind that you might want to run the command below after deleting the .lfsconfig file:
git lfs push --all origin
This will sync the local repo’s LFS objects with the Git LFS service at the original Git host. It pushes any new binary blobs to their LFS service which may have been added after you moved the LFS service to Large Media.
Please let us know if there are any issues with the new build or deployed site.