{"id":27954,"date":"2020-01-24T16:34:18","date_gmt":"2020-01-24T21:34:18","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=27954"},"modified":"2020-01-24T16:34:18","modified_gmt":"2020-01-24T21:34:18","slug":"setting-up-gitweb-on-shared-hosting","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/01\/24\/setting-up-gitweb-on-shared-hosting\/","title":{"rendered":"Setting Up Gitweb on Shared Hosting"},"content":{"rendered":"

Jordan Rose<\/a> (tweet<\/a>):<\/p>\n

I did get a few recommendations for other places to host Git repositories, but—at least partly inspired by Tom Ryder’s “Why Not GitHub?<\/a>”—I decided to take the plunge and set up my own hosting.<\/p>\n

[…]<\/p>\n

According to the Git Book<\/a>, you’re supposed to grab the latest sources and generate a custom version of the script yourself. What they don’t mention is that pretty much everything you’d customize by generating it yourself is already customizable with a config file.<\/p>\n

[…]<\/p>\n

The idea to use a RewriteRule is adapted from the gitweb man page<\/a>, but I’ve made one important change: paths that resolve to real directories are still sent to gitweb.cgi.<\/em><\/p>\n

[…]<\/p>\n

Basically, git doesn’t normally keep around info for clones to work over plain HTTP, but we can generate it up front whenever there’s a push. We use a post-update hook<\/a> for that.<\/p><\/blockquote>\n\n

Previously:<\/p>\n