amtrack / buildpack-gitlab

Dokku buildpack for GitLab

Buildpack: GitLab

Note: This project is currently unmaintained. Please get in touch with me via this issue if you're interested in taking over maintenance.

This is a Buildpack for GitLab to be used in combination with the heroku-buildpack-ruby through heroku-buildpack-multi.

How does it work?

While the buildpack-gitlab will setup gitlab-shell and do some magic,

the heroku-buildpack-ruby will take care of gitlabhq itself.

Getting started

Requirements

1. A PaaS like
   • dokku
   • dokku-alt
   • heroku (it has only an ephemeral filesystem)
2. At least 1GB of RAM and swap enabled
3. A redis and (postgres or mariadb) addon
4. Additional persistent storage
5. Additional port forwarding for the SSH port

General instructions

Tell your PaaS to use the multi buildpack:

BUILDPACK_URL=https://github.com/ddollar/heroku-buildpack-multi.git

with the buildpacks buildpack-gitlab and heroku-buildpack-ruby:

$ git checkout -b deployment
$ echo -e "https://github.com/amtrack/buildpack-gitlab.git\nhttps://github.com/heroku/heroku-buildpack-ruby.git" > .buildpacks
$ git add .buildpacks
$ git commit -m "prepare for deployment"

PaaS specific instructions

Depending on your PaaS, see the detailed instructions for

• creating the application
• managing required addons
• managing persistent storage and
• managing port forwarding

PaaS	Instructions
dokku	https://github.com/amtrack/buildpack-gitlab/wiki/dokku
dokku-alt	https://github.com/amtrack/buildpack-gitlab/wiki/dokku-alt

Environment variables

SMTP_URL

Setting the SMTP credentials in the syntax smtps://<user>:<password>@<smtp_url>/?domain=<domain>

Example:

SMTP_URL=smtps://john.doe:[email protected]/?domain=gmail.com

GITLAB_SHELL_VERSION

Specifying the gitlab-shell version.

Currently the default gitlab-shell version will be read from the file GITLAB_SHELL_VERSION. If you want to use another version you can set the environment variable GITLAB_SHELL_VERSION (mind prefixing the version number with a v in the environment variable).

Example:

GITLAB_SHELL_VERSION=v2.0.0

Info

Most of the GitLab Installation stuff is borrowed from

• sameersbn/docker-gitlab

This buildpack was generated with the Yeoman generator generator-buildpack

Known Issues

See here

buildpack-gitlab's Issues

Add to installation page?

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.

Error on push

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?

Replace MariaDB with PostgreSQL

Recommend by gitlab installation guide

Sidekiq doesn't start

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.

permission problems

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

gitlab-shell version should be configurable

Introduce an environment variable to make this configurable.

Looking for a new maintainer

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.

Use Data Volume Containers instead of Data Volumes