[WIP] First try to support both CE and EE in gdk

I tested it on a fresh installation.

• CE and EE are stored in the ce and ee subdirs respectively, each having its own repositories, gitlab-shell and authorized_keys
• One postgres and redis instance
• I removed some references to gitlab-runner as it was using the deprecated one.

Caveats

• currently it is duplicated code :/ but works
• gitlab-workhorse in the Procfile uses ce/gitlab/public as the document root dir, which seems to work with EE as well

Tree structure

.
├── Gemfile
├── Gemfile.lock
├── LICENSE
├── Makefile
├── Procfile
├── Procfile.example
├── README.md
├── Vagrantfile
├── ce
│   ├── gitlab
│   ├── gitlab-shell
│   └── repositories
├── database.yml.example
├── docker
│   ├── Dockerfile
│   ├── README.md
│   └── assets
├── ee
│   ├── gitlab
│   ├── gitlab-shell
│   └── repositories
├── gitlab-openldap
│   ├── Makefile
│   ├── README.md
│   ├── bin
│   ├── bootstrap.ldif
│   ├── etc
│   ├── frontend.alt.example.com.ldif
│   ├── frontend.example.com.ldif
│   ├── include
│   ├── lib
│   ├── libexec
│   ├── openldap-2.4.40
│   ├── openldap-2.4.40.tgz
│   ├── run-slapd
│   ├── run-slapd-alt
│   ├── sbin
│   ├── share
│   ├── slapd.d
│   └── var
├── gitlab-workhorse
│   ├── CHANGELOG
│   ├── LICENSE
│   ├── Makefile
│   ├── README.md
│   ├── VERSION
│   ├── archive.go
│   ├── artifacts.go
│   ├── authorization.go
│   ├── authorization_test.go
│   ├── deploy_page.go
│   ├── deploy_page_test.go
│   ├── development.go
│   ├── development_test.go
│   ├── error_pages.go
│   ├── error_pages_test.go
│   ├── git-http.go
│   ├── gitlab-workhorse
│   ├── handlers.go
│   ├── handlers_test.go
│   ├── helpers.go
│   ├── helpers_test.go
│   ├── lfs.go
│   ├── logging.go
│   ├── main.go
│   ├── main_test.go
│   ├── proxy.go
│   ├── proxy_test.go
│   ├── sendfile.go
│   ├── sendfile_test.go
│   ├── servefile.go
│   ├── servefile_test.go
│   ├── support
│   ├── test
│   ├── uploads.go
│   ├── uploads_test.go
│   └── upstream.go
├── gitlab.socket
├── postgresql
│   └── data
├── redis
│   ├── redis.conf
│   ├── redis.conf.example
│   ├── redis.socket
│   └── resque.yml.example
└── support
    └── edit-gitlab.yml

28 directories, 59 files

cc @jacobvosmaer @sytses @dzaporozhets

README.md

@@ -389,7 +389,7 @@ you don't want to use the Makefile, the steps you need to manually perform are:
 ### Update GitLab CE
-In order to fetch the latest code, first make sure that `foreman` for
+If you are developing on GitLab CE, first make sure that `foreman` for
 postgres is running (needed for db migration) and then run:
 ```
@@ -402,16 +402,16 @@ migrations. You can also update them separately by running
 ### Update GitLab EE
-If you are developing on GitLab EE, you can update GitLab EE and its gitlab-shell
-with:
+If you are developing on GitLab EE, first make sure that `foreman` for
+postgres is running (needed for db migration) and then run:
 ```bash
 make ee/update
 ```
-This will update both GitLab CE and `gitlab-shell` and run any possible
+This will update both GitLab EE and `gitlab-shell` and run any possible
 migrations. You can also update them separately by running
-`make ce/gitlab-update` and `make ce/gitlab-shell-update` respectively.
+`make ee/gitlab-update` and `make ee/gitlab-shell-update` respectively.
 ### Update gitlab-workhorse