commit d9cf1ef03fc218d571d541d229ecb17fae9ed789 from: Stefan Sperling date: Thu Apr 20 17:33:28 2023 UTC add gitwrapper man page to web site commit - 4202fd2e9073cadc3b74a1223c8ff56c67adb08d commit + d9cf1ef03fc218d571d541d229ecb17fae9ed789 blob - /dev/null blob + 72cf8a4a1bd5fc5f35da05345e24409e03490f39 (mode 644) --- /dev/null +++ gitwrapper.1.html @@ -0,0 +1,148 @@ + + + + + + + GITWRAPPER(1) + + + +
GITWRAPPER(1) + General Commands Manual + GITWRAPPER(1)
+
+
+

+

gitwrapper — + invoke an appropriate Git repository + server

+
+
+

+ + + + + +
gitwrapper -c + ‘git-receive-pack + repository-path’
+
+ + + + + +
gitwrapper -c + ‘git-upload-pack + repository-path’
+
+
+

+

At one time, the only Git repository server software easily + available was built into git-upload-pack(1) and git-receive-pack(1) which are part of the + git(1) suite. As a result of + this, most Git client implementations had the path and calling conventions + expected by git(1) compiled + in.

+

Times have changed, however. On a modern system, the administrator + may wish to use one of several available Git repository servers, such as + gotd(8).

+

It would be difficult to modify all Git client software typically + available on a system, so most of the authors of alternative Git servers + have written their programs so that they use the same calling conventions as + git-upload-pack(1) + and git-receive-pack(1) and may be put into place in their stead.

+

Although having drop-in replacements for + git-upload-pack(1) + and git-receive-pack(1) helps in installing alternative Git servers, it + essentially makes the configuration of the system depend on hard installing + new programs in /usr. This leads to configuration + problems for many administrators, since they may wish to install a new Git + server without altering the system provided /usr. + (This may be, for example, to avoid having upgrade problems when a new + version of the system is installed over the old.) They may also have a + shared /usr among several machines, and may wish to + avoid placing implicit configuration information in a read-only + /usr.

+

The gitwrapper program is designed to + replace git-upload-pack(1) and git-receive-pack(1) and to invoke an appropriate Git server + based on configuration information placed in + gotd.conf(5). This + permits the administrator to configure which Git server is to be invoked on + the system at run-time. Git repositories which are listed in + gotd.conf(5) and exist + on the filesystem will be served by gotsh(1). Any other Git repositories will be served by + git-upload-pack(1) + and git-receive-pack(1) as found in Git's libexec + directory, which is /usr/local/libexec/git/ by + default on OpenBSD.

+
+
+

+
+
+
Set the path to the configuration file for gotd(8). If not specified, the default path + /etc/gotd.conf will be used.
+
+
+
+

+

Configuration for gotd(8) is kept in /etc/gotd.conf.

+

git-upload-pack and + git-receive-pack are typically set up as a symlink + to gitwrapper which is not usually invoked on its + own.

+
+
+

+

got(1), + gotd.conf(5), + gotd(8), + mailwrapper(8)

+
+
+

+

Stefan Sperling + <stsp@openbsd.org>

+
+
+

+

The entire reason this program exists is a crock. Instead, a + command for invoking a Git server should be standardized or the Git protocol + should be changed to make the path to the program discoverable by Git + clients.

+
+
+
April 20, + 2023 OpenBSD 7.3
+ + blob - 7da654eb8e972d48a958c2f4f97eea1048b5f0f7 blob + 03ece1efff6b15fe4f341235c82cfab44dba5300 --- manual.html +++ manual.html @@ -38,5 +38,10 @@ Manual pages installed by the gotd package:
  • gotctl — control the Game of Trees Daemon
  • gotsh — Game of Trees Shell +Manual pages installed by the gitwrapper package: + +