Git over ssh and gitolite

[git-wiki.git] / pep-git.txt

diff --git a/pep-git.txt b/pep-git.txt
index 8e3e0c5d95f0591035fb09edb910b27361dc503f..25f6cfbcbc92cb8829f6bda87ab95b4c5c3d9835 100644 (file)
--- a/pep-git.txt
+++ b/pep-git.txt
@@ -793,14 +793,28 @@ information. To include git information in the prompt use
 <https://git.kernel.org/cgit/git/git.git/tree/contrib/completion/git-prompt.sh>`_.
 Read the detailed instructions in the file.
 
+Search the Net for "git prompt" to find other prompt variants.
+
 
 git on server
 =============
 
-TODO: anonymous access (``git daemon``); git over ssh; gitolite;
-gitweb; cgit; Kallithea; pagure; gogs and gitea; gitlab.
-
-http://gitolite.com/gitolite/index.html
+The simplest way to publish a repository or a group of repositories is
+``git daemon``. The daemon provides anonymous access, by default it is
+read-only. The repositories are accessible by git protocol (git://
+URLs). Write access can be enabled but the protocol lacks any
+authentication means, so it should be enabled only within a trusted
+LAN. See ``git help daemon`` for details.
+
+Git over ssh provides authentication and repo-level authorisation as
+repositories can be made user- or group-writeable (see parameter
+``core.sharedRepository`` in ``git help config``). If that's too
+permissive or too restrictive for some project's needs there is a
+wrapper `gitolite <http://gitolite.com/gitolite/index.html>`_ that can
+be configured to allow access with great granularity; gitolite has a
+lot of documentation.
+
+TODO: gitweb; cgit; Kallithea; pagure; gogs and gitea; gitlab.
 
 https://git.kernel.org/cgit/git/git.git/tree/gitweb