-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passwordless use case? #29
Comments
I would think this should be achievable by putting the user:pass in the lfs url like so:
But that doesn't seem to work. |
We can make the test server work without authentication, but the client side doesn't support that very well just yet. We'll need to modify the client to only ask for authorization if the server needs it. We don't currently support user/password in the urls store in the git config, but that may change. I think it's bad form to have the credentials checked into the repo, but it has been requested before. |
Yeah. It's bad form for sure. I was only trying everything I can think of to get a public server working. I'm think the "right" way to solve the problem is to have an option in the server to disable authentication and a client that respects that. I'm not holding my breath for all those changes to be made though. I had hoped I could find a way to make a public repo today. |
Don't #33 and git-lfs/git-lfs#415 resolve this ? |
#33 and git-lfs/git-lfs#415 only deal with the Batch API specifically. We kept it that way in the client to avoid breaking changes with the non-batched API, with the intent that in 0.6+ the Batch API will replace the other one. |
so isn't the uses:pass@server working yet? |
is the user@server format at least working? anyone tried that? |
On the latest client (1.2.1) and test server (0.3.0), I have
in my |
I'd like to use this test server to setup a public repository with some lfs-server backed files that, when cloned, does not prompt the user for a user name or password to pull the lfs files (just like any old public git repository on github). Is that possible?
It would be nice if there were an environment variable that could disable authentication or something like that.
The text was updated successfully, but these errors were encountered: