Thanks for your report and sorry to hear of your issues.

Is this launched from AWS Marketplace? Or the Hub?

Also can you please confirm the TurnKey version? If you are not sure, please post the output of "turnkey-version".

Regardless, I have opened an issue on our tracker: https://github.com/turnkeylinux/tracker/issues/691

[update] I have just confirmed this issue in v14.1. Apologies that this slipped through our testing. We'll work on a fix.

However, I haven't been able to pin down the cause just yet. However, I haven't been able to reproduce the issue with a new repo. I can successfully add a new git repo and that works as you'd hope.

This is the process step-by-step that I used to test:

1. Make new repo:

   mkdir -p /srv/repos/git/tester
   cd /srv/repos/git/tester
   git config --global user.name "test committer"
   git config --global user.email "test@example.com"
   git init
   echo "this is a test file" > test-file
   git add .
   git commit -m "initial commit"
   

2. Create new project:
   • "Projects" > "New Project"
   • I called mine "test-project" and used that for the identifier as well.
   • Click Create
   • Browse to new project, click Settings tab; click Repositories sub-tab
   • Click "New Repository"
   • Select "Git" from SCM dropdown, other details as relevant
   • For URL I used the file path to .git subdir of my git repo:

     /srv/repos/git/tester/.git

   • Click create
3. browse to new repo and there it is! :)

I just re-read your OP and also the tutorial that you said you followed and compared it to what I just wrote. The significant difference is that those instructions point to the base directory of the git repo; rather than the .git sub-directory (which contains all the git info like commits etc).

Looking at the source code for the appliance it appears that the build code (when the appliance was last rebuilt) made the same mistake. I'm not sure if this is due to some sort of change in Redmine or git, or whether it's been a regression in our build code. The fact that the tutorial you link to also makes the same mistake makes me think that something must have changed in Redmine and/or git...

Regardless, it turns out that the bug was noted previously and a fix provided for the appliance, but the app hasn't been rebuilt since then... So silly me just wasted a ton of time on something that was already fixed... Doh! So we just need to rebuild the appliance so this bug is no longer there...