GitLab

Created by: brianhay-energetica

I have Gitlab successfully setup with git repos in /home/git/repositories

I can push to, commit to and pull from these repos and everything shows up fine in the Gitlab interface.

However, I also need another web-based application (on the same server) to have read access to some repos. The web app devs recommend doing a git clone --bare into web-app-root/work/git/ which I did. I then (as root user) need to change the permissions on the new clone folder so that apache can access, BUT as soon as I do this the origin repo in /home/git/repositories/ gets messed up. I can no longer push to it (I get an error saying that it is corrupt) and Gitlab throws a 500 error each time I try to access the project in the Gitlab interface.

When I go back into /home/git/repositories/ the user:group is still the correct git:git

This makes no sense to me. How would changing the permissions of a cloned repo on the same box affect the origin repo?

I must be misunderstanding something.

Any ideas?