- 29 Mar, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 03 Mar, 2017 2 commits
-
-
Pawel Chojnacki authored
-
Alejandro Rodríguez authored
This will be necessary when adding gitaly settings. This version doesn't make any functional changes, but allows us to include this breaking change in 9.0 and add the needed extra settings in the future with backwards compatibility
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 14 Feb, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 27 Oct, 2016 1 commit
-
-
tiagonbotelho authored
only.
-
- 30 Aug, 2016 1 commit
-
-
Dirk Hörner authored
This commit fixes a typo where the mode argument to FileUtils.mkdir() would be passed in decimal rather than octal format, yielding bad permissions.
-
- 11 Aug, 2016 1 commit
-
-
bogdanvlviv authored
Since version ruby-2.2.0, method `File::exists?` is deprecated.
-
- 25 Jul, 2016 1 commit
-
-
Stan Hu authored
Set permissions of backup dir to g+s Closes #20188
-
- 30 Jun, 2016 1 commit
-
-
Alejandro Rodríguez authored
-
- 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
-
- 03 Nov, 2015 1 commit
-
-
Robert Speicher authored
Closes #3311
-
- 30 Jul, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 29 Jul, 2015 1 commit
-
-
Jacob Vosmaer authored
This sidesteps problems with running 'chmod' on some CIFS mounts.
-
- 19 Mar, 2015 1 commit
-
-
Administrator authored
-
- 30 Nov, 2014 1 commit
-
-
Achilleas Pipinellis authored
ProjectWiki.new() creates a new wiki git repository, so any tries to bare clone a bundle fail. With this patch we remove the newly created wiki.git before restoring from the backup bundle.
-
- 29 Nov, 2014 1 commit
-
-
Achilleas Pipinellis authored
-
- 20 Nov, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 13 Nov, 2014 1 commit
-
-
Dimitry Andric authored
If a project is being restored, but there is no bundle file, the project was empty when it was backed up. In this case, just use git init --base to create a new bare repository.
-
- 05 Nov, 2014 1 commit
-
-
Ciro Santilli authored
-
- 20 Oct, 2014 2 commits
-
-
Jacob Vosmaer authored
We need to skip empty repositories when creating a backup. Before this change, we were asking gollum-lib if the wiki contains any _pages_. Now we ask gitlab_git if the repository contains _files_. This should resolve gollum_lib Grit timeouts in the backup script.
-
Jacob Vosmaer authored
We need to skip empty repositories when creating a backup. Before this change, we were asking gollum-lib if the wiki contains any _pages_. Now we ask gitlab_git if the repository contains _files_. This should resolve gollum_lib Grit timeouts in the backup script.
-
- 01 Oct, 2014 1 commit
-
-
Jacob Vosmaer authored
This change also shows the output of failed Git commands during the backup.
-
- 08 Sep, 2014 1 commit
-
-
Jacob Vosmaer authored
The rewrite-hooks.sh script is a deprecated wrapper for gitlab-shell's create-hooks script.
-
- 08 May, 2014 1 commit
-
-
Jacob Vosmaer authored
This fixes a bug where wiki repositories for projects with an empty main repository would not get backed up.
-
- 09 Apr, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 26 Feb, 2014 1 commit
-
-
Jacob Vosmaer authored
The backup restore code for repositories was assuming that gitlab-shell is installed in /home/git/gitlab-shell. This commit changes that to use the configuration setting from gitlab.yml that specifies the path where gitlab-shell is installed.
-
- 06 Nov, 2013 1 commit
-
-
Jacob Vosmaer authored
-
- 05 Nov, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
This reverts commit c46eaca9.
-
- 04 Nov, 2013 1 commit
-
-
Nigel Kukard authored
- Database name may contain characters which are not shell friendly - Database password could contain the same - While we at it there is no harm in escaping generated paths too - Refactored 2-line system(command) Signed-off-by: Nigel Kukard <nkukard@lbsd.net>
-
- 10 Oct, 2013 1 commit
-
-
Jacob Vosmaer 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.
-
- 10 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 Apr, 2013 3 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-