Documentation: HTTP needs update-server-info.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Dec 17, 2005 at 11:39 UTC
80248b2e4888a05adcb903f53af84ee513d22245
3 files changed
+25
-10
Documentation/everyday.txt
+11
@@ -424,3 +424,14 @@ for branch policy control.
424
david is the release manager and is the only person who can
425
create and push version tags.
426
------------
427
+
428
+HTTP server to support dumb protocol transfer.::
429
++
430
+------------
431
+dev$ git update-server-info <1>
432
+dev$ ftp user@isp.example.com <2>
433
+ftp> cp -r .git /home/user/myproject.git
434
+
435
+<1> make sure your info/refs and objects/info/packs are up-to-date
436
+<2> upload to public HTTP server hosted by your ISP.
437
+------------
Documentation/git-update-server-info.txt
+3
-3
@@ -12,11 +12,11 @@ SYNOPSIS
12
13
DESCRIPTION
14
-----------
15
-A dumb server that does not do on-the-fly pack generations can
15
+A dumb server that does not do on-the-fly pack generations must
16
have some auxiliary information files in $GIT_DIR/info and
17
$GIT_OBJECT_DIRECTORY/info directories to help clients discover
18
-what references and packs the server has and make optimized
19
-pull decisions. This command generates such auxiliary files.
18
+what references and packs the server has. This command
19
+generates such auxiliary files.
20
21
22
OPTIONS
Documentation/tutorial.txt
+11
-7
@@ -1091,9 +1091,10 @@ lacks and transfers (close to) minimum set of objects.
1091
HTTP(S)::
1092
`http://remote.machine/path/to/repo.git/`
1093
+
1094
-HTTP and HTTPS transport are used only for downloading. They
1095
-first obtain the topmost commit object name from the remote site
1096
-by looking at `repo.git/info/refs` file, tries to obtain the
1094
+Downloader from http and https URL
1095
+first obtains the topmost commit object name from the remote site
1096
+by looking at the specified refname under `repo.git/refs/` directory,
1097
+and then tries to obtain the
1098
commit object by downloading from `repo.git/objects/xx/xxx\...`
1099
using the object name of that commit object. Then it reads the
1100
commit object to find out its parent commits and the associate
@@ -1104,7 +1105,9 @@ sometimes also called 'commit walkers'.
1105
The 'commit walkers' are sometimes also called 'dumb
1106
transports', because they do not require any git aware smart
1107
server like git Native transport does. Any stock HTTP server
1107
-would suffice.
1108
+that does not even support directory index would suffice. But
1109
+you must prepare your repository with `git-update-server-info`
1110
+to help dumb transport downloaders.
1111
+
1112
There are (confusingly enough) `git-ssh-fetch` and `git-ssh-upload`
1113
programs, which are 'commit walkers'; they outlived their
@@ -1517,12 +1520,13 @@ A recommended workflow for a "project lead" goes like this:
1520
2. Prepare a public repository accessible to others.
1521
+
1522
If other people are pulling from your repository over dumb
1520
-transport protocols, you need to keep this repository 'dumb
1521
-transport friendly'. After `git init-db`,
1523
+transport protocols (HTTP), you need to keep this repository
1524
+'dumb transport friendly'. After `git init-db`,
1525
`$GIT_DIR/hooks/post-update` copied from the standard templates
1526
would contain a call to `git-update-server-info` but the
1527
`post-update` hook itself is disabled by default -- enable it
1525
-with `chmod +x post-update`.
1528
+with `chmod +x post-update`. This makes sure `git-update-server-info`
1529
+keeps the necessary files up-to-date.
1530
1531
3. Push into the public repository from your primary
1532
repository.