buildpack-gitlab icon indicating copy to clipboard operation
buildpack-gitlab copied to clipboard

permission problems

Open amtrack opened this issue 11 years ago • 3 comments

After creating a new project via the web interface the new repository located in /home/git/repositories is owned by root:root. This makes it impossible for the git user to push to that newly created repository.

Workaround The current workaround is to fix that permission problems manually via

chown -R dokku:dokku /opt/gitlab

every time a new project has been created.

Ideas to fix this problem Read this first. Gitlab assumes that it is installed into /home/git/gitlab and the processes run as the user git. Dynos on the other hand have /app as current working directory and the user is root (in dokku) or a random user uXXXXXX(in heroku).

Possible solutions

  • make gitlab run as user git (gitlab-shell already runs as user git) or
  • make gitlab create files as git user or
  • change the user or the current working directory (impossible?)

amtrack avatar Jun 15 '14 13:06 amtrack

Hi @amtrack. I saw your post in GitLab room on Gitter. I think your best bet is to get gitlab running as the git user. That's what gitlab and gitlab-shell are expecting and it will solve this issue. I'm not familiar enough with dokku or heroku to say what that will take, though.

dblessing avatar Jun 15 '14 18:06 dblessing

Hmm, okay. I'll see if this is possible. If you'll ever find someone running gitlab as another user successfully, please tell me :smile:

amtrack avatar Jun 15 '14 20:06 amtrack

It shouldn't be an issue to run as another user but you need to make sure all components use the same user - unicorn, sidekiq, gitlab-shell.

On Jun 15, 2014, at 3:13 PM, Matthias Rolke [email protected] wrote:

Hmm, okay. I'll see if this is possible. If you'll ever find someone running gitlab as another user successfully, please tell me

— Reply to this email directly or view it on GitHub.

dblessing avatar Jun 15 '14 20:06 dblessing