Autogenerated HTML docs for v1.5.1-rc1-13-g0872

diff --git a/howto-index.html b/howto-index.html
index a0caa2201f6818f0a62b7cd04c19947318f55e25..c46404a4d2526dc7da521b0fb29f3306f3164d7a 100644 (file)
--- a/howto-index.html
+++ b/howto-index.html
@@ -365,6 +365,11 @@ into which branch and who can make a tag.</p>
 <ul>\r
 <li>\r
 <p>\r
+<a href="howto/use-git-daemon.txt">use-git-daemon</a>\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
 <a href="howto/using-topic-branches.txt">using-topic-branches</a> by tony.luck@intel.com\r
 </p>\r
 </li>\r
@@ -375,7 +380,7 @@ as a Linux subsystem maintainer.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 14-Feb-2007 07:23:40 UTC\r
+Last updated 20-Mar-2007 09:18:09 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/howto-index.txt b/howto-index.txt
index cd806a3b9f4d6768919375061f0ccaf5e0f565a3..79b58c4b8886bed5e700fe6ee3e1a438746c4332 100644 (file)
--- a/howto-index.txt
+++ b/howto-index.txt
@@ -73,6 +73,10 @@ implement repository maintenance policies, such as who can push
 into which branch and who can make a tag.
 
 
+* link:howto/use-git-daemon.txt[use-git-daemon] 
+
+
+
 * link:howto/using-topic-branches.txt[using-topic-branches] by tony.luck@intel.com
 
 In this article, Tony Luck discusses how he uses GIT

diff --git a/howto/use-git-daemon.txt b/howto/use-git-daemon.txt
new file mode 100644 (file)
index 0000000..1a1eb24
--- /dev/null
+++ b/howto/use-git-daemon.txt
@@ -0,0 +1,52 @@
+How to use git-daemon
+
+Git can be run in inetd mode and in stand alone mode. But all you want is
+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.
+