ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Git integration problem

Added by Georgios Petrou at 2012-09-21 07:07 pm

Hello everyone,

I followed the tutorial for setting up the advanced git integration with chiliproject
https://www.chiliproject.org/projects/chiliproject/wiki/HowTo_configure_ChiliProject_for_advanced_git_integration?version=6

When I run

git.exe clone --progress -v "http://MY_IP/repository"

I get prompted for a username and password and then I get

Cloning into 'C:\Users\Georgios\Desktop\repository'...
error: The requested URL returned error: 500 while accessing http://MY_IP/repository/info/refs
fatal: HTTP request failed

Also apache error.log reports
AuthUserFile not specified in the configuration

My apache config file is as follows

<VirtualHost _default_:80>
    ServerName MY_IP

    ServerAdmin MY_EMAIL

    DocumentRoot /var/www/grack/public

    PerlLoadModule Apache::Redmine

    <Directory /var/www/grack/public>
        Options None
        AllowOverride None
        Order allow,deny
        Allow from all
    </Directory>

    <Location "/repository">
        AuthType Basic
        AuthName "Git repository"    
        Require valid-user

        PerlAccessHandler Apache::Authn::Redmine::access_handler
        PerlAuthenHandler Apache::Authn::Redmine::authen_handler

        RedmineDSN "DBI:mysql:database=chiliproject;host=localhost" 

        RedmineDbUser "chiliproject" 
        RedmineDbPass "MY_PASSWORD" 

        RedmineGitSmartHttp yes

    </Location>

    ErrorLog /var/log/apache2/error.log

    LogLevel warn
    CustomLog /var/log/apache2/chiliproject.log combined

</VirtualHost>    

Any ideas what might be wrong?


Replies (1)

RE: Git integration problem - Added by Felix Schäfer at 2012-09-28 11:18 am

The Location block probably should target / instead of /repository.

From what I can gather your grack serves repositories on http://MY_IP/, so the repository to ProjectA would be http://MY_IP/projecta, to ProjectB it would be http://MY_IP/projectb and so on. The Location block however assumes the repositories would be http://MY_IP/repository/projecta and http://MY_IP/repository/projectb.

(1-1/1)