FM / howto

/usr/share/doc/git/howto

Name	Size	Mode	Actions
coordinate-embargoed-releases.html	29838	0644	edit dl rm
coordinate-embargoed-releases.txt	10823	0644	edit dl rm
keep-canonical-history-correct.html	26249	0644	edit dl rm
keep-canonical-history-correct.txt	6795	0644	edit dl rm
maintain-git.html	41732	0644	edit dl rm
maintain-git.txt	18220	0644	edit dl rm
new-command.html	22001	0644	edit dl rm
new-command.txt	4460	0644	edit dl rm
rebase-from-internal-branch.html	24456	0644	edit dl rm
rebase-from-internal-branch.txt	6310	0644	edit dl rm
rebuild-from-update-hook.html	20387	0644	edit dl rm
rebuild-from-update-hook.txt	3137	0644	edit dl rm
recover-corrupted-blob-object.html	23884	0644	edit dl rm
recover-corrupted-blob-object.txt	5510	0644	edit dl rm
recover-corrupted-object-harder.html	36038	0644	edit dl rm
recover-corrupted-object-harder.txt	14607	0644	edit dl rm
revert-a-faulty-merge.html	30865	0644	edit dl rm
revert-a-faulty-merge.txt	10856	0644	edit dl rm
revert-branch-rebase.html	24740	0644	edit dl rm
revert-branch-rebase.txt	7823	0644	edit dl rm
separating-topic-branches.html	20526	0644	edit dl rm
separating-topic-branches.txt	3356	0644	edit dl rm
setup-git-server-over-http.html	30562	0644	edit dl rm
setup-git-server-over-http.txt	8613	0644	edit dl rm
update-hook-example.html	23272	0644	edit dl rm
update-hook-example.txt	6289	0644	edit dl rm
use-git-daemon.html	19649	0644	edit dl rm
use-git-daemon.txt	2135	0644	edit dl rm
using-merge-subtree.html	20235	0644	edit dl rm
using-merge-subtree.txt	3025	0644	edit dl rm
using-signed-tag-in-pull-request.html	26765	0644	edit dl rm
using-signed-tag-in-pull-request.txt	8282	0644	edit dl rm

Edit: /usr/share/doc/git/howto/use-git-daemon.txt (2135B)

Content-type: text/asciidoc

How to use git-daemon
=====================

Git can be run in inetd mode and in stand alone mode. But all you want is
to let a coworker pull from you, and therefore need to set up a Git server
real quick, right?

Note that git-daemon is not really chatty at the moment, especially when
things do not go according to plan (e.g. a socket could not be bound).

Another word of warning: if you run

$ git ls-remote git://127.0.0.1/rule-the-world.git

and you see a message like

fatal: The remote end hung up unexpectedly

it only means that _something_ went wrong. To find out _what_ went wrong,
you have to ask the server. (Git refuses to be more precise for your
security only. Take off your shoes now. You have any coins in your pockets?
Sorry, not allowed -- who knows what you planned to do with them?)

With these two caveats, let's see an example:

$ git daemon --reuseaddr --verbose --base-path=/home/gitte/git \
	  --export-all -- /home/gitte/git/rule-the-world.git

(Of course, unless your user name is `gitte` _and_ your repository is in
~/rule-the-world.git, you have to adjust the paths. If your repository is
not bare, be aware that you have to type the path to the .git directory!)

This invocation tries to reuse the address if it is already taken
(this can save you some debugging, because otherwise killing and restarting
git-daemon could just silently fail to bind to a socket).

Also, it is (relatively) verbose when somebody actually connects to it.
It also sets the base path, which means that all the projects which can be
accessed using this daemon have to reside in or under that path.

The option `--export-all` just means that you _don't_ have to create a
file named `git-daemon-export-ok` in each exported repository. (Otherwise,
git-daemon would complain loudly, and refuse to cooperate.)

Last of all, the repository which should be exported is specified. It is
a good practice to put the paths after a "--" separator.

Now, test your daemon with

$ git ls-remote git://127.0.0.1/rule-the-world.git

If this does not work, find out why, and submit a patch to this document.

cmd: