As explained in the tips and tricks section of this guide, we'll want Pageant to automatically load your key when it starts. In the TortoiseHg installation folder, you'll find a helper tool called Pageant. You don't need to run the main Putty application itself.Äownload TortoiseHg if you haven't already. Save the file as id_rsa.ppk inside the same. PuTTY can still import it even though it doesn't even display it by default. Note: In the open dialog, you need to change the dialog to display "all files" in order to see the id_rsa key. Use PuTTyGen to create a id_rsa.ppk key from the id_rsa key using the instructions here: Inside the PuTTY installation folder you'll also find PuTTyGen. You can change Windows settings to show hidden files and folders if you want to be able to have a bit better overview.Äownload PuTTY. ssh (inside your user folder), which is hidden by default. Now you should have a id_rsa private key and id_rsa.pub public key inside a folder called. I assume you already have one, and in this guide we don't want to push with command line since we'll be using TortoiseHg. Ignore the rest, from "Creating a Mercurial repository" and forward. Use the instructions here to generate an SSH key and add it to sourcehut: Getting TortoiseHg on Windows to work with SourceHut's SSH authentication Like running the main PuTTy application, or running tortoiseplink, or editing your mercurial.ini file. But remember the guide omits all the things I read I should do and which I thus attempted, but it didn't work, and eventually turned out not to be needed anyway. When you read this guide, you might think it doesn't sound that complicated after all. So now I'm writing my own half-baked guide, mostly for my future self in case I need it again, but others might stumble over it and maybe find it useful too I guess. I couldn't remember anything, so had to figure it all out all over again. I got it all to work around a year ago, but I recently wiped my hard drive and needed to do it all over. Getting SSH to work involved juggling things like multiple types of SSH keys and formats all placed in a hidden folder, many different helper tools, and reading dozens of half-baked how-to guides that all contradict each other, often assume prior knowledge, and that are all for slightly different use cases which means they didn't quite work for me. Unlike BitBucket, SourceHut does not allow HTTPS authentication, so you have to use SSH, and nobody ever sat down and made SSH easy to use on Windows. Now, SourceHut has been a pain to use in many ways for a non-technical person like me, but I've had the most pain at all trying to get SSH authentication to work. Why did I choose it then? The "just works" alternatives had pricing that just did not work for a game development use case. It's made for people who identify with hacking and tinkering and knowing all the technical stuff. SourceHut is the opposite of "it just works". I and many other Mercurial lovers have then had to find alternative hosting. And BitBucket was a hosting solution for Mercurial that was affordable and also just worked. I wouldn't really have cared about that, except it made BitBucket close down their support for Mercurial some time ago. Unfortunately Mercurial has become a niche choice as Git has achieved overwhelming popularity, largely due to GitHub. You can question my assertion, but my preference is my preference in any case.) (I don't want to get into an argument over this. This is one reason I strongly prefer Mercurial for source control over Git. Or at least I highly prefer if things just work, and I don't have to fiddle with settings and configurations. I'm a skilled programmer, but I'm not a technical person. You can skip to the header below for the actual guide.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |