From 34374a679d2ed5a1015e105a6e79321f8e3abcac Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 22 Mar 2021 10:58:12 -0400 Subject: [PATCH] comment --- ..._ceb528ff60b9c7544eae28292ef74ddb._comment | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 doc/tips/setup_a_public_repository_on_a_web_site/comment_8_ceb528ff60b9c7544eae28292ef74ddb._comment diff --git a/doc/tips/setup_a_public_repository_on_a_web_site/comment_8_ceb528ff60b9c7544eae28292ef74ddb._comment b/doc/tips/setup_a_public_repository_on_a_web_site/comment_8_ceb528ff60b9c7544eae28292ef74ddb._comment new file mode 100644 index 0000000000..8c5b8fd3bd --- /dev/null +++ b/doc/tips/setup_a_public_repository_on_a_web_site/comment_8_ceb528ff60b9c7544eae28292ef74ddb._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 8""" + date="2021-03-22T14:39:06Z" + content=""" +@tomdhunt a few problems could result in this error message. + +1. The .git/config file might not be readable by the web server, or some + similar problem might cause the web server to fail to serve it. + Just for example, a web server might be configured to not serve .git + directories, since exposing them can sometimes be a mistake. + The web server would have to fail with some problem other than a + 404 not found.. in that case there would be no error message. + +2. git might somehow be failing to parse the .git/config file once it is + downloaded. You would have to be running an older version of + git-annex to get this error message in that situation though; + recent versions display a different message if the config parse fails. + +I think that's all the possibilities. To determine which it is, +I suggest you download the .git/config file from the webserver yourself +(that would be `http://server.name/annex/.git/config` in your example), +and pass the downloaded file to `git config --list --file` to get git to +parse it, making sure git doesn't exit with an error. +"""]]