Furthermore, the most comprehensive howto that I came across elsewhere contained several instructions that were just plain wrong. You also have to figure it out from various places all over the web, and searches on Google and Stack Overflow proved to be surprisingly fruitless. However, setting it all up on Windows is not entirely straightforward, and there doesn’t seem to be a decent guide to it anywhere on the Internet: most of the instructions that you read assume that you’re using either (a) Linux or a Mac, (b) the command line, or (c) both. ![]() Github is, of course, a hosting facility for git repositories, as one would expect of a site whose name says what it means and means what it says.įortunately, it is quite possible to use Mercurial as a client against github repositories via the hg-git extension, and you can pull and push from one to the other pretty much losslessly. Nevertheless, some of us do have a preference for one over the other, and many Subversion refugees like me who do most of their work in Windows tend to lean towards Mercurial.īut there’s no denying that github is fast becoming the Facebook of open source programming (albeit hopefully without the unethical bits, Farmville, and people tagging you in embarrassing photos for all and sundry to see), and if you want to strut your stuff as a developer, that’s the place to do it. My reasoning (as with the reasoning of everyone else who takes sides in this particular debate) is entirely subjective, so we won’t belabour the point here too much. I’m going to get really controversial here and say that I think Mercurial is better than git. User ' hg' obviously belongs to unix group ' dev'.( Update: I’ve updated these instructions for Mercurial 1.6/TortoiseHg 1.1.) ![]() So that the user CANNOT specify which hosts to connect to. The file /etc/ssh/sshd_config of the firewall contains a line similar to: Match Group dev ssh/autorhized_keys file contains the public keys of all the users that must access the repository on the firewall there's a user named ' hg' whose.ppk format they have to be converted to a one-liner ssh key. use hg-gateway to add that user's key to the hg user on serverĪ note: putty tends to generate keys in.ssh/authorized_keys of user hg on firewall To allow a user access to the remote repo: destination: pick your local destination.source: ssh:// remote-dev/ repo-name (remote-dev has to match whatever you called your session in putty!).Your SSH access is restricted by hg-gateway. You should see something like Using username "hg".Īuthenticating with public key "imported-openssh-key" from agent auto-login username: hg (or whatever user on the repository server has hg-gateway running).in 'telnet command or local proxy' replace content with ' FULLPATH\plink.exe -v -nc %host:%port (note use the FULL path of executable plink.exe. ![]() username: hg (or whatever user on the firewall has your public ssh key in.port: 22 (or whatever appropriate to ssh into the firewall).proxy hostname: your firewall DNS entry or IP address.save session as ' remote-dev' (any name is ok).into hostname put: your repository server's IP address.select your PRIVATE key you saved before, insert passphrase.right-click on the icon in the icon bar, 'add key'.run a windows command prompt (start > run and type 'cmd') and launch 'pageant.exe'.send your sysadmin the PUBLIC KEY not the private key! (sysadmins: read below). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |