From: Gary Yang <garyyang6@yahoo.com>
To: git@vger.kernel.org
Subject: Challenge of setting up git server (repository). Please help!
Date: Thu, 20 Nov 2008 13:39:12 -0800 (PST) [thread overview]
Message-ID: <829533.97868.qm@web37906.mail.mud.yahoo.com> (raw)
I am working on setting up a git server so that people can clone, pull and push their code at git.mycompany.com/pub/git+project path.
However, I am having challenges. For people who setup their git servers, please share your experneces with me and tell me what I did wrong.
I greatly appreciate it.
After I made configurations, I ran the command, git update-server-info at the public repository machine. But, I got the error.
git pull http://git.mycompany.com/pub/git/u-boot.git HEAD
fatal: http://git.mycompany.com/pub/git/u-boot.git/info/refs not found: did you run git update-server-info on the server?
The file /pub/git/u-boot.git/info/refs dose exist.
cat /pub/git/u-boot.git/info/refs
87ee4576c4c31b7046fe2bbbdf309eaba5c3f346 refs/heads/master
My question:
Is the contet of /pub/git/u-boot.git/hooks/post-update correct? Should I change "exec git-update-server-info" to "exec git update-server-info"?
cat /pub/git/u-boot.git/hooks/post-update
#!/bin/sh
#
# An example hook script to prepare a packed repository for use over
# dumb transports.
#
# To enable this hook, rename this file to "post-update".
exec git-update-server-info
I tried and changed "exec git-update-server-info" to "exec git update-server-info" in /pub/git/u-boot.git/hooks/post-update. But, I still got same error.
git pull http://git.mycompany.com/pub/git/u-boot.git HEAD
fatal: http://git.mycompany.com/pub/git/u-boot.git/info/refs not found: did you run git update-server-info on the server?
Which one is correct? "exec git-update-server-info" or "exec git update-server-info"? Eventhogh none of them working.
Below are my settings:
grep 9418 /etc/services
git 9418/tcp # Git Version Control System
grep git /etc/inetd.conf
git stream tcp nowait nobody /usr/local/libexec/git-core/git-daemon git-daemon --inetd --export-all /pub/git
cat /etc/xinetd.d/git-daemon
# default: off
# description: The git server offers access to git repositories
service git
{
disable = no
type = UNLISTED
port = 9418
socket_type = stream
wait = no
user = nobody
server = /usr/local/libexec/git-core/git-daemon
server_args = --inetd --export-all --base-path=/pub/git
log_on_failure += USERID
}
I am running git at Linux box:
uname -a
Linux svdclw004 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:56:44 EST 2007 x86_64 GNU/Linux
Are there anything wrong? Please let me know.
next reply other threads:[~2008-11-20 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 21:39 Gary Yang [this message]
2008-11-20 22:04 ` Challenge of setting up git server (repository). Please help! Asheesh Laroia
2008-11-20 22:13 ` Deskin Miller
2008-11-20 22:43 ` Gary Yang
2008-11-20 23:08 ` Deskin Miller
2008-11-20 23:48 ` Gary Yang
2008-11-20 23:54 ` Gary Yang
2008-11-20 23:59 ` J.H.
2008-11-21 0:12 ` Gary Yang
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 0:14 Gary Yang
2008-11-21 0:39 ` Gary Yang
2008-11-21 7:22 ` Mike Galbraith
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=829533.97868.qm@web37906.mail.mud.yahoo.com \
--to=garyyang6@yahoo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.