Pushing over SSH

[datashard]

More of a question than an actual Issue, because I'm kinda lost.

How do I get pushing over SSH to work when using the Docker Image / docker compose?

[datashard]

I'm guessing I might need a .ssh/authorized_keys file, since it looks like it does accept ssh connections lol

[icyphox]

I’m not entirely sure how you’re running the container, but in my K3s homelab I have my git repos on the host itself, and I push to it using the “git” user with a .ssh/authorized_keys file in its home directory. I then mount this home directory inside my legit container. Not sure if that helps.

[datashard]

It does! This confirms my earlier thought lmao

Guessing the .ssh/authorized_keys file would be in /home/git/.ssh/authorized_keys within the container?

[icyphox]

Hm, I haven't tried running ssh in the container since I push to the underlying host's /home/git (container has read-only access to this dir) but I suppose that could work as well.

[datashard]

I'll try it! :D

I'll report back if it works

[datashard]

Well, ssh-ing into the container doesn't work. Shouldn't be surprised since I doubt there's a SSH Server running in there? It doesn't even have (ba)sh so I should've figured that out sooner lol

Would you mind sharing the code for the way you push?
If I can't get it to work I might just run an hourly cron to cp certain things from my forgejo instance.

As for general http auth, you could theoretically try and use a htpasswd file? I haven't looked into it much but I think it should work?

[icyphox]

Oh, yeah, of course—there is no ssh inside the container. It's a very light image.

There isn't much "code" to share. I have the git repos on a machine and push over ssh as you would anywhere else. This directory of bare git repositories gets mounted inside my legit container. legit itself doesn't deal with any of the ssh pushing.

As for http auth, that isn't supported by legit (explicitly disabled). The recommended approach is what I described above. Bear in mind: legit is read-only. It will simply serve git repos in repo.scanPath. Populating that directory is the user's problem.

[datashard]

Trying to actually get this working on my end again, and I was wondering how you're setting up the repos on your end?

I've been trying to use git init --bare and pushing to it after, and while the repo exists on the server, I get a reference not found error in the logs, though when i copy over a repo from my forgejo instance, those just show up without any issues.

[datashard]

Yeah. I'm really lost about this and have been pulling my hair out trying to figure out what the difference between repos is. because even after pushing to the remote repo (made with git init --bare) it did not show up.

All I get from my Logs is getting head of /var/www/git/bare.git: reference not found, which doesn't really give me anything to figure out what I'm missing in the repo

[icyphox]

Hey! Hm, I can try and help you out on something quicker than here, if you prefer. Have you got Discord/email/…?

[icyphox]

But yeah, that's not really a "breaking" error per se. That's just legit complaining that it can't get the HEAD—the topmost ref, or commit, if you will—of the repository. And it can't get it because there isn't any: a newly initialized bare repo has no commits. So once you push a commit, it'll show up and the log message will go away.

[datashard]

Hey! Hm, I can try and help you out on something quicker than here, if you prefer. Have you got Discord/email/…?

I have Discord @fangmarks

But yeah, that's not really a "breaking" error per se. That's just legit complaining that it can't get the HEAD—the topmost ref, or commit, if you will—of the repository. And it can't get it because there isn't any: a newly initialized bare repo has no commits. So once you push a commit, it'll show up and the log message will go away.

That's the thing though, even after I pushed a commit, it still wasn't showing up

[datashard]

I... have no idea what the fuck I did but now it's showing up????

[icyphox]

lol, strange. Possibly wonky browser cache...? I can't be sure.

[runxiyu]

I've been trying to implement protocols natively (i.e., SSH directly handled in the forge daemon, without relying on OpenSSH or git-upload-pack/git-receive-pack) in my own Git forge for quite a while and it's a huge pain. I find go-git's documentation on network transports to be rather lacking.

• There's an old fork of legit that says it implements ssh pushing, I'm currently auditing it to see if it works
• Someone has an example of cloning via ssh, with go-git
• SSH pushing isn't implemented at all in my git forge, where anonymous SSH cloning still spawns an external git-upload-pack process

I suppose this is out of scope for legit? Though anonymous SSH cloning would definitely be nice (no need to trust PKI/CAs, etc.).