amtrack / buildpack-gitlab Goto Github PK

If you plan on maintaining this feel free to add it to https://about.gitlab.com/installation/ under community installation methods by sending an MR to https://gitlab.com/gitlab-com/www-gitlab-com/ and mentioning me.

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?)

I've followed the instructions on the Wiki Page step by step, but the second push gets rejected with the error message remote: /tmp/buildpackjrnC2/bin/compile: line 35: sudo: command not found. Anyone any idea why this happens?

I tried deploying GitLab 7.2.1 and have the problem of Sidekiq not starting. I have no experience with Rails or Dokku so I have no idea what might be the reason. Will dig deeper and report.

Introduce an environment variable to make this configurable.

Recommend by gitlab installation guide

Due to time constraints I can not continue this project currently.
If you are interested in taking over maintenance of this project please comment below.