Hi, @grupoibiracu and @furiouskj. We have a troubleshooting support guide for Large Media here:
If that guide doesn’t help please send us the following information:
the output of netlify lm:info
the output of git config -l
In your case, @grupoibiracu, you are not being logged in. First we need to get the following command working:
netlify login
If the login is successful, netlify status should show something like this:
$ netlify status
──────────────────────┐
Current Netlify User │
──────────────────────┘
Name: Luke Lawson
Email: something@example.com
Teams:
mu: Collaborator
We will need to resolve that before we can troubleshoot Large Media as you need a working Netlify CLI login to install the Large Media Git credential helper. You cannot push to Large Media without the Git credential helper and you cannot install the Git credential helper until you can login with Netlify CLI.
Please let us know if there are any questions and we look forward to getting additional information to troubleshoot.
I was logged in and have the latest versions of Git, LFS and Git Credentials.
The slug issue still happened.
I actually found another issue and fixed it. The lm plugin was looking for ~/.netlify/config.json which is never created on mac. There is one created in ~/Library/Preferences/netlify/… so I just copied that to the config.json path the git-credential tool was looking for.
Still the tool seems broken for fresh installs in mac using either homebrew or npm
Hi, @grupoibiracu. I think I found the issue with the site you wrote in about. The Large Media add-on is not configured at Netlify for this site. The solution for this would normally work like this:
delete the file .lfsconfig from the base of the repo
To summary those steps, you will run the following commands:
netlify link
netlify lm:setup
git add .lfsconfig
git commit -m 'install Large Media add-on at Netlify'
git push
After this occurs, the Large Media add-on will be added to the site and Netlify will become the host for the Git LFS files in the repo. This will allow the git push to succeed.
Hi, @furiouskj. To troubleshoot I still need the information requested previously above:
Would you please include that information here so we can assist with this issue?
I don’t have a .lfsconfig file. When I follow the steps for setup, I get TypeError: Cannot read propery 'slug' of undefined on netlify lm:setup after clicking authorize on the browser.
Netlify Status & Netlify lm:info
both returned normal.
Followed the Doc on Large Media Setup again. Netlify lm:setup
Returns the following after clicking “Authorise” in the browser: TypeError: Cannot read property 'slug' of undefined
Here it is: Checking Git version [2.30.0] Checking Git LFS version [2.13.2] Checking Git LFS filters Checking Netlify’s Git Credentials version [0.1.9]
In my case, config.json did exist under ~/.netlify, but it was missing a bunch of fields that were present in ~/Library/Preferences/netlify/config.json. So I replaced the ~/netlify copy with the ~/Library/Preferences/ one, and re-ran netlify lm:setup. This time, the command ran successfully and created the .lfsconfig, finally.
Yeah the solution from @alecazam also seems to work for me, though
When we onboard new people to our project, it is always takes a couple of hours to set up our site on someone’s computer and usually involves a lot of inspecting of various .config files across multiple computers, and re-trying all of the various installs multiple times. Having to do this fix is new for us.
In general, it seems super frictionless to set up netlify-cli, but never ends up being the case with our project which uses LFS. It seems that there could be better checks in netlify-cli or the LFS set up to catch the situation above