An error occurred fetching the project authors.
- 16 Aug, 2013 1 commit
-
-
Rovanion Luckey authored
Since it is easily could break installations running on the server - hence the person doing the install should be able to make the decision to remove himself.
-
- 14 Aug, 2013 1 commit
-
-
Jakub Kramarz authored
Isn't 5.4 current stable?
-
- 09 Aug, 2013 2 commits
-
-
Troy Murray authored
-
Sytse Sijbrandij authored
-
- 08 Aug, 2013 1 commit
-
-
Troy Murray authored
-
- 03 Aug, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 30 Jul, 2013 1 commit
-
-
Robert Schilling authored
-
- 29 Jul, 2013 1 commit
-
-
Jacob Vosmaer authored
-
- 22 Jul, 2013 1 commit
-
-
Axilleas Pipinellis authored
-
- 20 Jul, 2013 1 commit
-
-
Jeroen van Baarsen authored
-
- 19 Jul, 2013 1 commit
-
-
Lukas Elmer authored
-
- 18 Jul, 2013 3 commits
-
-
Jacob Vosmaer authored
-
Ariejan de Vroom authored
This reverts commit 670e1be7.
-
Ariejan de Vroom authored
This reverts commit b5cd66d4.
-
- 15 Jul, 2013 2 commits
-
-
Matt Woodward authored
Additional unicorn -> puma reference update
-
Matt Woodward authored
Updated incorrect/outdated references to unicorn.rb; changed to puma.rb
-
- 08 Jul, 2013 3 commits
-
-
Dmitriy Zaporozhets authored
-
Sytse Sijbrandij authored
-
Dmitriy Zaporozhets authored
-
- 06 Jul, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 03 Jul, 2013 1 commit
-
-
Andrew Gallagher authored
I've moved the instruction in question to the the 'Configure GitLab DB settings'. Can't change permission to a file that doesn't already exist
-
- 29 Jun, 2013 1 commit
-
-
Ariejan de Vroom authored
-
- 19 Jun, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 16 Jun, 2013 1 commit
-
-
Sytse Sijbrandij authored
Fix spelling error and make sure you never log in as git user so you never have to logout to run sudo.
-
- 12 Jun, 2013 1 commit
-
-
Sytse Sijbrandij authored
-
- 11 Jun, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 26 May, 2013 3 commits
-
-
Ben Bodenmiller authored
-
Ben Bodenmiller authored
-
Ben Bodenmiller authored
addresses gitlabhq/gitlabhq#3809
-
- 24 May, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 20 May, 2013 3 commits
-
-
Dmitriy Zaporozhets authored
-
Sytse Sijbrandij authored
-
Sytse Sijbrandij authored
-
- 18 May, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 16 May, 2013 1 commit
-
-
Robert Schilling authored
-
- 09 May, 2013 1 commit
-
-
Axilleas Pipinellis authored
Setting Git's global user.name and user.email are missing from instructions, causing check.rake to fail at this step. Signed-off-by: Axilleas Pipinellis <axilleas@archlinux.gr>
-
- 07 May, 2013 3 commits
-
-
Axilleas Pipinellis authored
Signed-off-by: Axilleas Pipinellis <axilleas@archlinux.gr>
-
Axilleas Pipinellis authored
By default there is no public/uploads directory when no attachments are uploaded. Prompt users to create the uploads directory during install otherwise the backup task will fail. Place mysqldump args in single quotes to avoid error if password contains special characters. Signed-off-by: Axilleas Pipinellis <axilleas@archlinux.gr>
-
crazyscience authored
For some reason, if the nginx configuration is bound to an IP, it breaks the install, causing all git clone/push/pull operations to die with a 'fatal: The remote end hung up unexpectedly' message. Changing this configuration seems to fix the problem. I reckon that this is just a temporary fix. I don't know the ins and outs of GitLab well enough to vouch for this change, but I do know that these instructions are broken, and that this update will fix them.
-
- 28 Apr, 2013 1 commit
-
-
Axilleas Pipinellis authored
-