-
Login as non-root user.
-
Install ruby with required version (2.4.4 at the time I wrote this), the gitlab site recommends using a ruby version manager (such as RVM, rbenv, chruby).
-
Source the required script after installing ruby version manager. (In case of RVM, it may be
~/.rvm/scripts/rvm
or/etc/profile.d/rvm.sh
depending on how you install RVM.) -
Install bundler by
gem install bundler
(though I think this step is unnecessary since it will be installed automatically later). -
Install git version 2.18 or higher.
-
Install an up-to-date node 8.x (LTS) and yarn 1.2 or newer. (Node 8.9 doesn't work since one of the dependencies requires 8.10 or higher)
-
Install Go 1.9.6 or newer.
-
Install Google Chrome 60 or newer with ChromeDriver version 2.33 or newer. Since Google Chrome is not free/libre, I suppose it can be supplanted by Chromium.
-
Install PostgreSQL 9.x (10.x is not yet supported).
-
Install GraphicsMagick.
-
Increase the watch limit of inotify for
webpack
andkarma
to track file changes effectively. (I increased it from 8K to 512K.) -
Install
libpq-dev
,redis-server
,libicu-dev
,cmake
,g++
,libre2-dev
,libkrb5-dev
,ed
, andpkg-config
if not already installed. -
Install
gitlab-development-kit
by executing the following commands.gem install gitlab-development-kit gdk init [DIRECTORY]
This will clone the GDK repository into
./gitlab-development-kit
if the optional directory name is not given.You now have two choices: develop in either a fork or the main repo. I followed the fork approach.
gdk install gitlab_repo=https://gitlab.com/YOUR-FORK/gitlab-ce.git support/set-gitlab-upstream
Then start up the GDK as follows.
gdk run
I created the script install.sh
which contains I did manually
setting up the GDK. I have not tested it but it should work.