Support LFS purely over SSH protocol

[ibigbug]

Feature Description

The current LFS related operations only using settings.AppURL as the endpoint:

gitea/services/lfs/server.go

Line 48 in bc6df18

return setting.AppURL + path.Join(rc.User, rc.Repo+".git", "info/lfs/objects", p.Oid)

One scenario is I want to have server.ROOT_URL(settings.AppURL) to be external faced URL to browse the site.

And I want to have server. SSH_DOMAIN to be my internal domain to clone and push code.

But the current implementation only looks at AppURL(ROOT_URL), should SSH_DOMAIN be considered for LFS operations?

Screenshots

No response

[lunny]

Hm, git-lfs has supported SSH protocol I think. ref: git-lfs/git-lfs#4446

[ibigbug]

good to know, but how to use it?

looks Gitea hasn't support it yet:

-> % ssh git@gitea.at.somewhere -p PORT git-lfs-transfer some/repo.git download

Gitea: Unknown git command
Gitea: Unknown git command

[lunny]

@ibigbug Could you change the title to support a pure ssh lfs protocol something like that?

Yes. Since that PR was merged recently, Gitea itself didn't support that at the moment. But it should fallback to use http/https protocol.

[ibigbug]

thanks @lunny

keen to see Gitea can make LFS over SSH work.

[ibigbug]

@lunny any updates?

[lunny]

@lunny any updates?

Nobody are working on this issue.

[ibigbug]

@lunny thanks for letting me know.

How to get someone to take a look at this?

[fcharlie]

In fact, it is not that difficult to implement git-lfs-transfer. We can write such a command based on rust/golang to support the git lfs pure ssh protocol.

bk2204 implements a great example:
https://github.com/bk2204/scutiger

Inside our company, I have used golang to simulate the git-lfs-transfer command in the ssh server from this project, and it is currently running stably.

[davama]

This feature would be great! 👍

[tionis]

@fcharlie did you end up using this project internally and did it work as expected or were there some complications?

[fcharlie]

@fcharlie did you end up using this project internally and did it work as expected or were there some complications?

Since the prune ssh protocol does not support OSS signature download, and AI needs to download a large number of large files, we disabled it for performance reasons.

Here is also an implementation reference for the SSH protocol:
https://github.com/charmbracelet/git-lfs-transfer

[algora-pbc]

💎 $300 bounty • CommitGo, Inc.

Steps to solve:

1. Start working: Comment /attempt #17554 with your implementation plan
2. Submit work: Create a pull request including /claim #17554 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to go-gitea/gitea!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🔴 @jemiluv8	Mar 11, 2024, 9:52:04 AM	WIP
🟢 @Sambit003	Apr 10, 2024, 4:13:13 PM	WIP
🟢 @ConcurrentCrab	Jun 21, 2024, 11:27:29 AM	#31516