git-http-backend - Linux


git-http-backend is a standalone HTTP server that allows clients to interact with a Git repository over HTTP. It is primarily used to provide read-only access to repositories via a network, enabling remote collaboration and distribution of code. It can handle HTTP requests for Git operations such as fetching, pushing, cloning, and listing references.


git-http-backend [options] <repository_path>


  • -a, –advertise-refs=: Advertise additional references not in the repository.
  • -p, –port=: Specify the port on which the HTTP server will listen (default: 9418).
  • -s, –stateless-rpc: Disable HTTP request pooling.
  • -u, –unix-socket=: Specify the path to a Unix domain socket.
  • -v, –verbose: Enable verbose logging.
  • -B, –base-path=: Specify the base path for the repository (default: /).
  • -C, –config-file=: Specify an alternate configuration file.
  • -P, –pid-file=: Specify the file to store the process ID.
  • –no-acl-check: Disable ACL checks.
  • –no-body-size-limit: Disable HTTP body size limit.
  • –no-retry-after-check: Disable use of Retry-After headers.
  • –max-connections=: Set the maximum number of concurrent connections.
  • –receive.fsckObjects: Enable checking for invalid objects on push.
  • –advertise-capabilities=: Advertise specific capabilities.


1. Start a simple Git HTTP server:

git-http-backend /my/repository

2. Listen on a specific port:

git-http-backend -p 8080 /my/repository

3. Disable stateless RPC:

git-http-backend -s /my/repository

4. Use a Unix domain socket:

git-http-backend -u /tmp/git-http.sock /my/repository

5. Advertise additional references:

git-http-backend --advertise-refs=my_refs-file /my/repository

Common Issues

1. Permission denied: Ensure that the user running the server has read permissions to the repository.

2. HTTP 404 Not Found: Check if the repository exists and is accessible via the specified path.

3. HTTP 500 Internal Server Error: Check the server logs for detailed error messages. Consider enabling verbose logging for more information.

4. SSL/TLS errors: If HTTPS is required, configure SSL/TLS certificates and ensure that the client trusts the server’s certificate.


git-http-backend can be integrated with other tools and workflows, such as:

  • Remote access: Use HTTP to access remote repositories for cloning, fetching, and pushing.
  • CI/CD pipelines: Integrate the HTTP server into CI/CD pipelines to enable automated build, test, and deployment.
  • Repository hosting: Create a public or private repository hosting service using the HTTP server.

Related Commands