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:
If the login is successful, netlify status should show something like this:
$ netlify status
Current Netlify User │
Name: Luke Lawson
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
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