Rubynaut: Git: Easy way to setup a private remote repository

Git: Easy way to setup a private remote repository

stephane — Tue, 04 Mar 2008 20:41:00 +0100

Git is different from svn and create a private repository on a remote server too. No need of gitosis or git-daemon for this.

I start from an existing project and a server I already access to with ssh key.

First, initialize git in your project:

git init
git add .
git commit -m 'initial import'

[update]

~~Then create a git copy of your project into a git archive my_project_folder.git.~~

~~git clone—bare my_project_folder my_project_folder.git~~

Copy ~~this archive~~ the .git folder to your remote server:

scp -rp .git user@server://path/to/repositories/my_project_folder.git

Add this new repository in the config of your local project:

git remote add my_remote_repo ssh://server/path/to/repositories/my_project_folder.git

You’re done. After a change you can commit and then push your change to the remote repo:

git commit -m "message for change log"
git push my_remote_repo

Use your own parameters for:

my_project_folder with the folder of your project
path/to/repositories with the path to your repository on the remote server
my_project_repo with the name you want for the remote repository, usually origin

If you need a public repository, have look to gitosis or git-daemon. Best is Github.

"Git: Easy way to setup a private remote repository" by RF

Thu, 06 Mar 2008 18:25:19 +0100

Jon Gretar, you should maybe checkout Mercurial (Hg), there’s even a TortoiseHg project. It’s a really great SCM (and fast)

"Git: Easy way to setup a private remote repository" by Chris

Thu, 06 Mar 2008 03:57:50 +0100

Yeah, it should ;)

"Git: Easy way to setup a private remote repository" by Rich

Thu, 06 Mar 2008 00:55:17 +0100

Don’t forget that your remote host has to have Git installed for this to work.

"Git: Easy way to setup a private remote repository" by Stephane

Wed, 05 Mar 2008 21:14:40 +0100

Ok, thanks for the comment.

Should it even be:

scp -r .git remotehost:new_repo.git

"Git: Easy way to setup a private remote repository" by Chris

Wed, 05 Mar 2008 18:39:03 +0100

How come you cloned your initial project? I usually just:

scp -r .git ssh://remotehost:new_repo.git

Then go from there.

"Git: Easy way to setup a private remote repository" by Stephane

Wed, 05 Mar 2008 12:48:44 +0100

You’re right, the learning curve is harder with git than with svn and for new users it’s not simplifying life, at first. That’s why I published this post to show an “easy” way of using git. Currently I only use clone, commit, and push.

"Git: Easy way to setup a private remote repository" by Jon Gretar

Wed, 05 Mar 2008 12:02:17 +0100

Hey I’m not judging. ;)

After watching the Peepcode screencast I decided not to go to Git. Just seemed to overly complicate things somehow when most users just simply need to know the “svn add” and “svn commit” commands and they are good for life. :)

"Git: Easy way to setup a private remote repository" by Stephane

Wed, 05 Mar 2008 11:53:41 +0100

This post is more about using git than moving from svn to git. But for my own experience, I did move to git because it’s much faster and open new ways of social collaboration, as you can see on Github. Also I’d prefer to make several local commits and then a bigger commit to a central repo rather than always push small changes to the repo, and I m not always connected. A last point, git is pretty well integrated in Textmate now.

Being said, people are free to use whatever SCM they like :)

"Git: Easy way to setup a private remote repository" by Jon Gretar

Wed, 05 Mar 2008 09:32:01 +0100

Call me old fashioned…. But I still haven’t found any reason for why I should move to git from Subversion. I have no need for local repos since I’m always network connected. The easy branching would be nice but really isn’t a must for me. But I would miss all the tools that would be missing.

And I keep hearing about how amazing it is to have many repositarys for the code. But I haven’t really heard why it would be an advantage. Unless you have 20+ developers on the project working on the same code. And that’s not common.