GitLab Development Kit merge requestshttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests2015-01-04T11:08:39Zhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/6Set ARCHFLAGS to install postgres gem2015-01-04T11:08:39Zusername-removed-2900Set ARCHFLAGS to install postgres gemPostgres gem needs special ARCHFLAGS otherwise bundle fails with following error:
```
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby -r ./...Postgres gem needs special ARCHFLAGS otherwise bundle fails with following error:
```
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby -r ./siteconf20140807-68013-1kd9tnb.rb extconf.rb
checking for pg_config... yes
Using config values from /usr/local/bin/pg_config
checking for libpq-fe.h... yes
checking for libpq/libpq-fs.h... yes
checking for pg_config_manual.h... yes
checking for PQconnectdb() in -lpq... no
checking for PQconnectdb() in -llibpq... no
checking for PQconnectdb() in -lms/libpq... no
Can't find the PostgreSQL client library (libpq)
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.
```
This is documented also when installing the postgres gem:
```
When installing the postgres gem, including ARCHFLAGS is recommended:
ARCHFLAGS="-arch x86_64" gem install pg
```https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/11Replace shell test user2014-08-25T09:14:03Zusername-removed-1164jeroenvanbaarsen@gmail.comReplace shell test user**What does this MR do?**
it makes sure that we also change the `user` in the test environment
**Why is this MR needed?**
If we dont change this, people will run into errors when running the tests:
```
git clone 'https://git...**What does this MR do?**
it makes sure that we also change the `user` in the test environment
**Why is this MR needed?**
If we dont change this, people will run into errors when running the tests:
```
git clone 'https://gitlab.com/gitlab-org/gitlab-shell.git' 'tmp/tests/gitlab-shell/'
Cloning into 'tmp/tests/gitlab-shell'...
remote: Counting objects: 1332, done.
remote: Compressing objects: 100% (879/879), done.
remote: Total 1332 (delta 792), reused 717 (delta 400)
Receiving objects: 100% (1332/1332), 190.34 KiB | 0 bytes/s, done.
Resolving deltas: 100% (792/792), done.
Checking connectivity... done.
git fetch origin && git reset --hard $(git describe v1.9.6 || git describe origin/v1.9.6)
bin/install
mkdir: /home/git/.ssh: Operation not supported
bin/install failed
rake aborted!
Command failed with status (1): [bin/install...]
/Users/jeroen/Development/gitlab/gitlab/lib/tasks/gitlab/shell.rake:49:in `block (4 levels) in <top (required)>'
/Users/jeroen/Development/gitlab/gitlab/lib/tasks/gitlab/shell.rake:24:in `chdir'
/Users/jeroen/Development/gitlab/gitlab/lib/tasks/gitlab/shell.rake:24:in `block (3 levels) in <top (required)>'
Tasks: TOP => gitlab:shell:install
(See full trace by running task with --trace)
```
**Belongs to what issues?**
#8 https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/20Set 3000 port for web app in gitlab.yml 2014-09-23T15:52:12Zusername-removed-444Set 3000 port for web app in gitlab.yml According to this line https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/Makefile#L43 we want GitLab be on port 3000. But gitlab.yml use old 80 port from sample config. This MR fixes itAccording to this line https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/Makefile#L43 we want GitLab be on port 3000. But gitlab.yml use old 80 port from sample config. This MR fixes itusername-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/46Add mac note2015-03-17T12:47:44ZDrew BlessingAdd mac noteI ran into an issue installing `libv8` gem on Mac OS X 10.10.2. Adding a note to help others if they run into this.I ran into an issue installing `libv8` gem on Mac OS X 10.10.2. Adding a note to help others if they run into this.https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/47Add 'ed' to arch linux docs2015-03-31T12:53:00Zusername-removed-66948Add 'ed' to arch linux docshttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/52include option that does not install ci2015-09-03T14:08:22Zusername-removed-5332include option that does not install ci* Include make option that skips installation of CI
* Minor formatting cleanup in README* Include make option that skips installation of CI
* Minor formatting cleanup in READMEhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/57Replace gitlab-runner with gitlab-ci-multi-runner2016-04-12T11:36:27Zusername-removed-5302Replace gitlab-runner with gitlab-ci-multi-runnerKamil TrzcińśkiKamil Trzcińśkihttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/61fix root default password2015-07-16T15:50:25Zusername-removed-63948fix root default passwordJust update the default root passwordJust update the default root passwordhttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/68Make gitlab-git-http-server work with nginx2015-09-04T13:04:53ZStan HuMake gitlab-git-http-server work with nginxusername-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/81Fix the port number given. Listed 3000 though 4000 is used in the command on ...2015-11-10T16:16:26Zusername-removed-123742Fix the port number given. Listed 3000 though 4000 is used in the command on the previous line.Fix an apparent typo.Fix an apparent typo.https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/86ci-multi runner replaces depricated runner2015-11-16T11:43:08ZZeger-Jan van de Wegzegerjan@gitlab.comci-multi runner replaces depricated runnerI've got no experience in writing makefiles, so please be aware.
Fixes #67 I've got no experience in writing makefiles, so please be aware.
Fixes #67 https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/88Fix port (4000 instead of 3000) in README2015-11-20T15:40:49Zusername-removed-128633Fix port (4000 instead of 3000) in READMENothing much more to say, really. :)Nothing much more to say, really. :)https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/92Add make serve command to spawn foreman2015-12-03T15:20:26ZAchilleas PipinellisAdd make serve command to spawn foremanI was tired typing `bundle exec foreman start` all the time (although I have this in an alias), so `make serve` made more sense.
Also did some minor cleanup.I was tired typing `bundle exec foreman start` all the time (although I have this in an alias), so `make serve` made more sense.
Also did some minor cleanup.username-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/93[WIP] Add switcher2016-02-24T10:25:29ZValery Sizov[WIP] Add switcherThis tool can be used as CE/EE switcher
```
switch ce
switch ee
```
There is a little convention: your database names should be prefixed with `_ce` and `_ee` and the same with repositories folder (you should have two folders `re...This tool can be used as CE/EE switcher
```
switch ce
switch ee
```
There is a little convention: your database names should be prefixed with `_ce` and `_ee` and the same with repositories folder (you should have two folders `repositories` and `repositories_ee` or `repositories_ce`).
In other words, this switcher just replaces prefixes in your database.yml and renames folders `repositories` to `repositories_ce` and `repositories_ee` to `repositories`. That's ithttps://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/94[WIP] First try to support both CE and EE in gdk2016-02-24T10:25:14ZAchilleas Pipinellis[WIP] First try to support both CE and EE in gdkI 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 ...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 https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/97Bind Workhorse on all interfaces2016-01-11T11:55:11ZGrzegorz BizonBind Workhorse on all interfacesBind workhorse on `0.0.0.0:3000`.
This change in `Procfile.example` makes it possible to use Workhorse in raw Docker container, without mapping container ports using Docker mechanisms.
It can be now available by accessing Docker co...Bind workhorse on `0.0.0.0:3000`.
This change in `Procfile.example` makes it possible to use Workhorse in raw Docker container, without mapping container ports using Docker mechanisms.
It can be now available by accessing Docker container directly through `docker0` interface (like `172.17.0.1:3000`).username-removed-5302username-removed-5302https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/132Add ruby-version as a link2016-03-24T13:22:32Zusername-removed-428933Add ruby-version as a linkThis is a soft-link that links to `gitlab/.ruby-version`. This then ensures that the version of Ruby that is used when running matches.
Closes #106.This is a soft-link that links to `gitlab/.ruby-version`. This then ensures that the version of Ruby that is used when running matches.
Closes #106.https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/141Add steps to take when "Database 'gitlabhq_development' does not exist" is en...2016-05-26T03:15:38Zusername-removed-479648Add steps to take when "Database 'gitlabhq_development' does not exist" is encountered.This error was the source of quite some difficulty for me. I would like to save others the time.This error was the source of quite some difficulty for me. I would like to save others the time.https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/144WIP: Escape spaces and parens in path2016-04-22T14:56:00ZMark PundsackWIP: Escape spaces and parens in pathTries to fix #114 but is incomplete so far. Spaces and parentheses in the path need to be escaped in a few more places.Tries to fix #114 but is incomplete so far. Spaces and parentheses in the path need to be escaped in a few more places.https://staging.gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/146Fix workhorse-stunnel bash syntax2016-05-04T03:00:49Zusername-removed-444214Fix workhorse-stunnel bash syntax