From 53d4947cd6cdd80f9c9fe3960096ff7dd434bb70 Mon Sep 17 00:00:00 2001
From: Geert Stappers <stappers@stappers.it>
Date: Thu, 31 Aug 2023 21:26:39 +0200
Subject: [PATCH] How to avoid 'Repository not exported'

Go to the `.git` directory and create file `git-daemon-export-ok`.
---
 README.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/README.md b/README.md
index 7117fc4..d3b9c29 100644
--- a/README.md
+++ b/README.md
@@ -142,3 +142,21 @@ Afterwards, bring up the container with `docker-compose up` to make sure everyth
 When you get `message: "repository path '/git/orzklv-dots/' is not owned by current user"` in the
 logging, it means exactly that. It is a _git design choice_, only owner writes to the git
 repository. Match the `uid` what `rgit` started with the `uid` of the git repo on the filesystem.
+
+##### Repository not exported
+
+Message `Git returned an error: Repository not exported` is like _"repo not yet exposed"_.
+
+Go to the `.git` directory and create file `git-daemon-export-ok`.
+
+```text
+$ cd /srv/rgit/rgit.git
+$ ls
+HEAD      config       hooks  objects      refs
+branches  description  info   packed-refs
+$ touch git-daemon-export-ok
+$ ls
+HEAD      config       git-daemon-export-ok  info     packed-refs
+branches  description  hooks                 objects  refs
+$
+```
--
libgit2 1.7.2