From: Alan Chandler <alan@chandlerfamily.org.uk>
To: git@vger.kernel.org
Subject: succesfull use of git-shell
Date: Wed, 9 Nov 2005 21:52:07 +0000 [thread overview]
Message-ID: <200511092152.07195.alan@chandlerfamily.org.uk> (raw)
I just wanted to give a heads-up on a successful set up and push to a
repository where the account accessing the repository runs git-shell.
It turned out to be extremely simple to do - but the documentation that I
could find is so terse in places that I wasn't sure it was going to work
until I tried it. Two main issues.
1) the man page for git-push describes <repository> as
remote.machine:/path/to/repo.git/
the tutorial isn't much help either as it says
git push <public-host>:/path/to/my-git.git master
whereas I knew I wanted to access an account that was different from mine
2) the directory paths are always specified as absolute in the documentation,
but (particularly if you are going to set up a public repository which
several people may be pushing to) its helpful not to know exactly which path
on the server the repository exists.
In my setup I did the following simple things
1) created an account called git with a home directory at /var/lib/git and a
shell of /usr/local/bin/git-shell (you can see where my git is installed) on
my server (called roo.home)
2) created a an empty repository at /var/lib/git/famtree.git
a) Logged in as root into the machine that was the server
b) Became a git user with
su -s /bin/bash git
(You can't do a normal su git because the default shell immediately throws you
straight out again)
c) mkdir famtree.git; GIT_DIR=famtree.git git-init-db
d) chmod +x famtree.git/hooks/post-update
(planning to allow http anonymous access)
3) back on my development machine - pushed the master branch of my current
repository out to the new one just created with
git-push git@roo.home:famtree.git
It is this last simple command line that I _really_ like. If I wanted to set
up some form of centralised development with multiple access to the
repository, I only have to append the public keys of those people into the
authorized_keys file on that account on the server and I am done.
--
Alan Chandler
http://www.chandlerfamily.org.uk
Open Source. It's the difference between trust and antitrust.
next reply other threads:[~2005-11-09 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 21:52 Alan Chandler [this message]
2005-11-09 22:00 ` succesfull use of git-shell Alan Chandler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511092152.07195.alan@chandlerfamily.org.uk \
--to=alan@chandlerfamily.org.uk \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox