Gitlist cannot get anything beyond repository list

gitgitolite

I am trying to setup gitlist on CentOS Linux (with gitolite in case that matters — I have relaxed the permissions on the repo directories managed by gitolite).

I extracted the version 0.3 tarball from today from gitlist.org.

My config.ini looks like this:

client = '/usr/bin/git' ; Your git executable path
repositories = '/home/gitolite/repositories/' ; Path to your repositories

[app]
debug = true    
; I don't know if baseurl is still needed..seems like my results are the same either way
baseurl = 'http://sub.example.com.com/gitlist' ; Base URL of the application

virtual host directive in httpd.conf:

<VirtualHost *:80>
  DocumentRoot /var/www/html
  ServerName sub.example.com
  <Directory "/var/www/html">
    AllowOverride All
    Options -Indexes
  </Directory>
</VirtualHost>

htaccess:

<IfModule mod_rewrite.c>
  Options -MultiViews

  RewriteEngine On
  RewriteBase /var/www/html/gitlist/

  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule ^(.*)$ index.php [L,NC]

  AuthName "Git List"
  AuthType Basic
  AuthUserFile /var/www/.gitlistpwds
  Require valid-user

</IfModule>
<Files config.ini>
  order allow,deny
  deny from all
</Files>

With this setup, going to http://sub.example.com/gitlist results in the browser error message saying that /index.php does not exist (i.e. it's trying to go to /var/www/html/index.php )

In this case if I go to http://sub.example.com/gitlist/index.php, the repository list (apparently) properly appears. When I click on one of the repos, something goes wrong when it tries to execute, git. I get:

Whoops, looks like something went wrong.

1/1 RuntimeException: Unknown option: -c
(std git usage message omitted)

If I remove the rewrite rule from .htaccess, I am able to access the index page by either specifying index.php or not. But in that case when I click on a repo, it tries to find the repo underneath the gitlist directory:

The requested URL /gitlist/testing.git/ was not found on this server.

Can someone please help sort out this mess?

Best Answer

I finally managed to test gitlist.

I removed the .htaccess, and kept the following config in httpd.conf:

# GitList on 28473
<IfModule !php5_module>
  LoadModule php5_module modules/libphp5.so
</IfModule>
Listen 28473
<VirtualHost aserver.prod.fr.company:28473>
    ServerName aserver.prod.fr.company
    ServerAlias aserver
    SSLCertificateFile "/home/vonc/apache/crt"
    SSLCertificateKeyFile "/home/vonc/apache/key"
    SSLEngine on
    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
    SetEnv GIT_HTTP_BACKEND "/home/vonc/usr/local/apps/git/libexec/git-core/git-http-backend"
    DocumentRoot /home/vonc/gitlist/github
    Alias /gitlist /home/vonc/gitlist/github
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
      SSLOptions +StdEnvVars
    </FilesMatch>
    <FilesMatch ".php$">
      SetHandler application/x-httpd-php
    </FilesMatch>
    <FilesMatch ".phps$">
      SetHandler application/x-httpd-php-source
    </FilesMatch>
    <Directory /home/vonc/gitlist/github>
        SSLOptions +StdEnvVars
        Options ExecCGI +Indexes +FollowSymLinks
        AllowOverride All
        order allow,deny
        Allow from all
        Options -MultiViews

        DirectoryIndex index.php
        RewriteEngine On

        RewriteBase /home/vonc/gitlist/github/
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteRule ^(.*)$ gitlist/index.php/$1 [L,NC]

    </Directory>

    # RewriteLog "/home/vonc/gitlist/logs/apache_gitlist_rewrite_log"
    # RewriteLogLevel 3
    CustomLog "/home/vonc/gitlist/logs/apache_gitlist_ssl_request_log" \
              "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
    ErrorLog "/home/vonc/gitlist/logs/apache_gitlist_error_log"
    TransferLog "/home/vonc/gitlist/logs/apache_gitlist_access_log"
    LogLevel info
</VirtualHost>

(From my own commit, and this setup)

Note that:

  • this is for running gitlist in its own subdirectory: https://myServer/gitlist (not just https://myserver)
  • It won't display any files under a subdirectory within a git repo: see Issue 250, the patch is pending
Related Topic