Skip to content
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

Command-line tests #59

Open
mslinn opened this issue Dec 29, 2024 · 0 comments
Open

Command-line tests #59

mslinn opened this issue Dec 29, 2024 · 0 comments

Comments

@mslinn
Copy link

mslinn commented Dec 29, 2024

It would be helpful to be able to test this program from the command line. However, the scant documentation makes this a challenge.

Presumably, the git command-line client with the Git LFS extension invokes git-lfs-transfer with the path from lfs.url stored in .lfsconfig. So, if a git user types the following from the top-level directory of a git repo:

$ git config -f .lfsconfig lfs.url ssh://mslinn@gojira/mnt/_/work/git/eval_bare_repo

Then .lfsconfig will have at least the following:

[lfs]
        url = ssh://mslinn@gojira/mnt/_/work/git/eval_bare_repo

... which (I think) means the Git command-line client will issue a command something like the following when fetching an LFS file:

ssh mslinn@gojira git-lfs-transfer /mnt/_/work/git/eval_bare_repo download

When I type the above incantation, the response is:

000eversion=1
000clocking
0000

And then the program appears to pause, awaiting input.

I would like to test upload and download. Is this possible? If so, how?

I am attempting to document two variations of this scenario: a bare git repo on a server, without a git server and without a Git LFS server.

  1. via ssh - the reason for this issue
  2. via samba / local protocol (file: URI schema) - you aren't concerned with this

Later I will move on to documenting the other scenarios, all of which involve a git server, and most of which involve a Git LFS server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant