- 03 Jun, 2016 1 commit
-
-
Connor Shea authored
Colorize is a gem licensed under the GPLv2, so we can’t use it in GitLab without relicensing GitLab under the terms of the GPL. Rainbow is licensed under the MIT license and does the exact same thing as Colorize, so Rainbow was added in place of Colorize. The syntax is slightly different for Rainbow vs. Colorize, and was updated in accordance. The gem is still a dependency of Spinach, so it’s included in the development/test environments, but won’t be packaged with the actual product, and therefore doesn’t require we relicense the product. An attempt at relicensing Colorize was made, but didn’t succeed as the library owner never responded. Rainbow library: https://github.com/sickill/rainbow Relevant issue regarding licensing in GitLab's gems: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3775
-
- 23 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 16 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 22 Mar, 2016 1 commit
-
-
Drew Blessing authored
-
- 19 Nov, 2015 1 commit
-
-
Marin Jankovski authored
-
- 10 Nov, 2015 1 commit
-
-
Kamil Trzcinski authored
- Offloads uploading to GitLab Workhorse - Use /authorize request for fast uploading - Added backup recipes for artifacts - Support download acceleration using X-Sendfile
-
- 15 Sep, 2015 1 commit
-
-
Kamil Trzcinski authored
-
- 23 Jun, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 02 Apr, 2015 1 commit
-
-
Valery Sizov authored
-
- 20 Nov, 2014 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 05 Aug, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 03 Jun, 2013 1 commit
-
-
Angus MacArthur authored
-
- 30 May, 2013 1 commit
-
-
Angus MacArthur authored
These fixes will allow a restore of gitlab when the backups and repositories directories are in non-standard locations (ie sub-dirs of gitlabhq). Also allows the restore to be run from script overriding the need of a user to confirm the rebuild of the authorized_keys file.
-
- 08 May, 2013 1 commit
-
-
Lev Abalkin authored
-
- 06 May, 2013 1 commit
-
-
Lev Abalkin authored
-
- 05 May, 2013 1 commit
-
-
Andrey Kumanyaev authored
-
- 23 Apr, 2013 1 commit
-
-
Angus MacArthur authored
If the backup directory is not sub the gitlab install directory, then the git rev-parse call will fail.
-
- 18 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 10 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 Apr, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 14 Mar, 2013 1 commit
-
-
Chris Lawlor authored
Uses ActiveRecord::Base.connection.quote_table_name. Fixes issue 2437.
-
- 11 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 31 Dec, 2012 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 23 Dec, 2012 1 commit
-
-
Riyad Preukschas authored
-
- 22 Dec, 2012 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 20 Dec, 2012 2 commits
-
-
Riyad Preukschas authored
Rename gitlab:app:db_* to gitlab:backup:db:* Rename gitlab:app:repo_* to gitlab:backup:repo:* Rename *_dump to *_create
-
Riyad Preukschas authored
-
- 22 Nov, 2012 1 commit
-
-
Gosuke Miyashita authored
In backup_create, backup information hash is using symbol as its key. But in backup_restore, string key is used and it returns empty value.
-
- 19 Nov, 2012 1 commit
-
-
Hugo Duksis authored
-
- 26 Sep, 2012 1 commit
-
-
Nihad Abbasov authored
-
- 02 Sep, 2012 1 commit
-
-
Sytse Sijbrandij authored
Merge branch 'master' into non-interactive-aws-install Conflicts: doc/installation.md Fix merge mess in installation.md
-
- 28 Aug, 2012 2 commits
- 25 Aug, 2012 1 commit
-
-
randx authored
-
- 27 Jul, 2012 1 commit
-
-
Michael van Rooijen authored
-
- 26 Jul, 2012 1 commit
-
-
Michael van Rooijen authored
Modified the `repo_dump` and `repo_restore` rake tasks to properly dump and restore repositories based on their `path` rather than their (project) `name`. The project name can be uppercase and may contain spaces. This caused the repository to be restored as a different `path` that it was initially created as, thus, breaking the `git remote` and the web interface can no longer detect the repository either because it searches by `path` and not by `name`. Also, when restoring the permissions are incorrect making it impossible to push new commits to the remote repository. So now on success it'll set the correct permissions (but requires that the `gitlab` user has `sudo` privileges, or this task must be executed as root).
-