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.

Problems with built-in advanced git integration

Added by Moritz von Buttlar at 2011-05-03 09:49 am

Hi,

I followed instructions on

HowTo_configure_ChiliProject_for_advanced_git_integration

but now I'm stuck. How should I generate the git repository, which URL should
I set in the project settings, and how do I access the repository from the command line (remotely) ?

git ls-remote http://git.opensource-solar.org/test.git asks me for an OpenSSH login and password.

I changed the project to public, so in principle read access should be possible without login, or not ?
Does ChiliProject also create the initial repository for me ?

I will extend the HowTo if I find out how it works :)

Moritz

Replies (3)

RE: Problems with built-in advanced git integration - Added by Felix Schäfer at 2011-05-04 07:49 am

Moritz von Buttlar wrote:

I followed instructions on

HowTo_configure_ChiliProject_for_advanced_git_integration

but now I'm stuck. How should I generate the git repository, which URL should
I set in the project settings, and how do I access the repository from the command line (remotely) ?

As you already seem to have discovered judging by your edit of the instructions: you need to put the full local path in the Repository tab of the project configuration in ChiliProject. This was not specified in the HowTo because ChiliProject only accepts local repos/paths for git repositories.

git ls-remote http://git.opensource-solar.org/test.git asks me for an OpenSSH login and password.

I changed the project to public, so in principle read access should be possible without login, or not ?

The problem is probably that your repository is called test.git. The name of the repository must be exactly the same as the identifier of the project you want to use the credentials from, without any extra .git. This is because the Redmine.pm (ChiliProject.pm) authentication and authorization module recognizes the repository name as the identifier of the project from which to use the credentials.

If you have a project with an identifier test, changing the name of your git repository from test.git to test should make things work. After that, access to the test repository over http will be granted to users with the "show repository" permission to read and the "commit to repository" permission to write to the repository.

Does ChiliProject also create the initial repository for me ?

It can, but doesn't on it's own. There's a script called reposman.rb that can be called from a cron to periodically poll your ChiliProject install, look for projects with the "Repository" module enabled but with no repository created yet, we haven't ported the docs yet though, so you'd have to look for this one on redmine.org I guess.

RE: Problems with built-in advanced git integration - Added by Moritz von Buttlar at 2011-05-04 07:25 pm

Thank you very much ! Everything is working now.

Moritz

RE: Problems with built-in advanced git integration - Added by Felix Schäfer at 2011-05-04 09:20 pm

Moritz von Buttlar wrote:

Everything is working now.

Great!

(1-3/3)