clone

Working on a site (DefinitiveDrupal.org) which is in its own big Git repository. But when working on a module that's custom to the site but probably will become generalized and contributed back, we simply git init in that module's directory to make it a repository too. No git submodules or other voodoo. In addition to getting us an independent commit history for that module, it gives us the ability to throw that module into other situations and work on it there.

http://github.com/guides/getting-a-copy-of-your-github-repo

This works for other people's repositories also, where you have been given access and when you have your public key.

For instance:

git clone git@github.com:scor/rdfx.git

Note: The agaric git repository is not public, but this approach will work on your own server.

Stefan-agaric wrote: copy your folders to your home dir on the server, cd to /srv/git and then run git clone --bare folder folder.git

From my laptop:

cd ~
scp -r customhome ben@grassrootsconnection.org:~/customhome

On the server:

ben@server:/srv/git/agaric$ git clone --bare ~/customhome customhome.git

Initialized empty Git repository in /srv/git/agaric/customhome.git/

And don't forget!

This function ("agc" stands for "Agaric Git Clone") is in my ~.bashrc (actually, a ~.bashrc-agaric that is included in my .bashrc) and takes care of several steps I always have to look up anyway. I recently extended it to be able to start a new project as well as bringing down a local copy of an existing one. This relies on and provides the first steps for the Capistrano scripts for deploying Agaric sites primarily developed by Stefan.