https://gitworkshop.dev/npub1ha6lk9d8gtpv42mazl9nahu7wupjmjf9y3y8tvj9gy9dc20etmts995yfr/nospm

Reply to this note

Please Login to reply.

Discussion

Keen to try this out. I'm not sure what git backend you are using but could you get it to set git config `uploadpack.allowTipSHA1InWant` and `uploadpack.allowUnreachable` to true on the repo to enable cloning with ngit via the nostr url?

Also add .git to the end of the git sever in the nip34 announcement, as the git server doesnt forward it?

The git backend is gitea, I tried those config changes on the cmdline, not sure if gitea honours that. I can't get the nostr:// cloning to work. Strange because regular cloning works fine.

Thanks for adding the .git to the git server url in the announcement. the standard gitea, or at least the OOTB version that is packaged for nix, comes with those flags set. I tried the gitea nix package locally and it worked ngit. Maybe there is something i can do to make ngit more forgiving.

The strange part is my http logs show multiple successful status = 200 requests from ngit and NO errors and ngit still fails. So I'm not sure where the problem is.

I wonder if it has something to do with the fact that I have not pushed any commits via nostr? Does ngit need a commit event or is the repo announcement enough?

It fallsback to using the git server for refs if it cant find a state event on nostr.