You can create another ssh key on the remote server and add it to your GitHub account.
Or probably what might be better, is to just set up the repository on the remote server using the Public Clone URL for your GitHub fork: git clone git://github.com/... You'll be able to pull updates from the your fork but won't be able to push changes made on the remote server back to it. Which from a process point of view would be the correct thing to do (make changes locally -> push to GitHub -> pull on remote server). While it's possible to set up the remote server to pull from your local repository directly, you'd have to 1. Have a static IP or get setup with a dynamic DNS service 2. Set up sshd or git-daemon locally 3. If you're behind a router that uses NAT, configure port forwarding to make your local machine accessible from outside your local network These aren't necessarily difficult things to do but it's a matter of whether it's worth your time since you already have a GitHub fork configured. Long On Tue, Jun 10, 2008 at 1:08 AM, Antony Evans <[EMAIL PROTECTED]> wrote: > > Thanks Long, helpful reply. I tried pulling from my forked repositary > on Github and get an SSH error (presumably because my remote server > doesn't have my private key). Is there a code to pull from my local > drive, which doesn't have a URL? > > Antony > > > -- Long Nguyen [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ Insoshi developer site: http://dogfood.insoshi.com/ Insoshi documentation: http://docs.insoshi.com/ You received this message because you are subscribed to the Google Groups "Insoshi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
