Hi, @Vaughan_Curd. Then there are two possible solutions:
- We can uninstall the Large Media add-on and you can use the Git LFS service provided by GitHub.
- You can add the
.lfsconfig file needed and use Large Media for the Git LFS service.
For option one, please read this support guide and then let us know when you are ready to proceed.
Once Large Media is uninstalled, the final two steps are:
- add the required environment variable
GIT_LFS_ENABLED=1 to the site settings here (which must be done in the Netlify web UI only -
netlify.toml won’t work for this as the value is needed before cloning and we only have the current
netlify.toml after cloning)
- trigger a new build of the site
For option two, the first step is to create the missing
.lfsconfig file. Just create a file with that name (no extension) in the base directory of the repo and add the following to it:
url = https://<SITE API ID HERE>.netlify.app/.netlify/large-media
You can get the site’s API ID on this page:
For example, if the API ID was “3d25f98b-c822-4ba8-ae5d-efaeb6052c90” (and it isn’t - but if it was), then the file
.lfsconfig would contain this:
url = https://3d25f98b-c822-4ba8-ae5d-efaeb6052c90.netlify.app/.netlify/large-media
That file then needs to be committed to the repo and pushed upstream.
Once this change is made, this will make Netlify’s Large Media service the Git LFS service for this repo. Remember, once this is done, the
git lfs push --all command can be used to sync the files in the local repo to Netlify’s Git LFS service (which is called “Large Media”). This will allow the images to be displayed when you browse the site.
Please let us know if there are questions about either solution or if you are ready for us to proceed with the Large Media uninstall.