{"thread":{"id":"39978","subject":"Documentation bug in ProGit v2","startedAt":"2015-07-31T10:13:38Z","lastAt":"2015-07-31T10:13:38Z","messageCount":1,"participants":["Hugo Connery"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"267193","messageId":"55BB4A52.2060404@env.dtu.dk","threadId":"39978","inReplyTo":null,"subject":"Documentation bug in ProGit v2","fromName":"Hugo Connery","fromEmail":"hmco@env.dtu.dk","sentAt":"2015-07-31T10:13:38Z","receivedAt":"2015-07-31T10:13:38Z","isPatch":false,"sender":{"key":"hmco@env.dtu.dk","avatar":null},"body":"Hi,\n\nWhen discussing establishing git over Smart HTTP on pages 140 and 141:\n\n[quote]\nFinally you’ll want to make writes be authenticated somehow, possibly\nwith an Auth block like this:\n\n<LocationMatch \"^/git/.*/git-receive-pack$\">\nAuthType Basic\n140GitWeb\nAuthName \"Git Access\"\nAuthUserFile /opt/git/.htpasswd\nRequire valid-user\n</LocationMatch>\n\nThat will require you to create a .htaccess file containing the\npasswords of all the valid users. Here is an example of adding a\n“schacon” user to the file:\n\n$ htdigest -c /opt/git/.htpasswd \"Git Access\" schacon\n[end quote]\n\nThis will 401 every time.  You either do:\n\nAuthType Digest and use htdigest, or you do\nAuthType Basic and use htpasswd\n\nApache recommend Basic + SSL rather than Digest.\n\nThanks for the book.\n\nRegards,  Hugo Connery\n--\nHead of IT, Department of Environmental Engineering\nTechnical University of Denmark,\n\n"}]}