cjb / GitTorrent

A decentralization of GitHub using BitTorrent and Bitcoin
MIT License
4.75k stars 262 forks source link

Easily finding mutable key? #55

Closed pdaian closed 9 years ago

pdaian commented 9 years ago

So I'm running gittorrentd on a repository, and even with debug mode on, there is nowhere I can see the mutable key printed out by the daemon. I've tried manually SHA1'ing the pub, and clone failed with hash not found.

I think there should be some output in gittorrentd to the effect of "Now serving [mutable key]/[repo name] over Gittorrent DHT and accepting new connections. Clone at gittorrent://[uri], and update by pushing to this local repository."

There is one line in the output to the effect of:

  bittorrent-dht [bd32ebb] new DHT bd32ebb5eb22f8b9bde7229754c70b12c8e95380 +0ms

While I thought this may be the key's hash, it does not work in clone (though I'm listening on 6881 with the port properly forwarded, and on a server with no forwarding required), and it changes every time I restart gittorentd (with the same ed25519.key). Also, it does not correspond to the sha1 of my "pub" key.

Edit: I see this is fixed in #28... feel free to close :+1:

E2: On further inspection, it looks like my gittorrentd is not successfully hosting. Full log here: http://pastebin.com/iNsKmm2Z Seems to be a repeat of #22 but my export file is touched. Tried on three separate machines, same result. What's going on here?

E3: I see, this needs to be run from the root Git directory, where each repo is a subdir (./*/.git/git-daemon-export must exist). This should be made clearer in the README, as well as where the repo name derives from (subdir name). Everything is working now, sorry about the spam :+1: