- 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
-
- 31 May, 2016 1 commit
-
-
Robert Speicher authored
This is idempotent, so there's no harm calling it if the directory already exists. Closes #12710
-
- 25 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 23 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 16 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 08 Feb, 2016 1 commit
-
-
Jeroen Nijhof authored
-
- 19 Nov, 2015 1 commit
-
-
Marin Jankovski authored
-
- 18 Nov, 2015 2 commits
-
-
Marin Jankovski authored
-
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
-
- 03 Nov, 2015 1 commit
-
-
Robert Speicher authored
Closes #3311
-
- 02 Nov, 2015 1 commit
-
-
Robert Speicher authored
-
- 16 Oct, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 06 Oct, 2015 6 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
Documentation elsewhere refers to this internal path, let's keep it.
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
By using light gzip compression we can save a lot of disk IO during the backup.
-
Jacob Vosmaer authored
During the backup we create an intermediate copy of two directories: builds and uploads. Instead of creating many small files with 'cp -r', we now use tar (and fast gzip) to create single intermediate files. This saves on disk IO and disk space while creating a backup.
-
- 25 Sep, 2015 1 commit
-
-
Paul Beattie authored
This adds support for AWS S3 SSE with S3 managed keys, this means the data is encrypted at rest and the encryption is handled transparently to the end user as well as in the AWS Console. This is optional and not required to make S3 uploads work.
-
- 18 Sep, 2015 1 commit
-
-
Valery Sizov authored
-
- 15 Sep, 2015 3 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 21 Aug, 2015 1 commit
-
-
Jacob Vosmaer authored
The change in baa15792 broke backup restore fucnctionality. This would not lead to data loss, but it prevented the restore script from working. This bug exists only in 7.14.0 release candidate versions, not in 7.13. Reported in https://github.com/gitlabhq/gitlabhq/issues/9571 .
-
- 12 Aug, 2015 1 commit
-
-
Ted Strzalkowski authored
command line.
-
- 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.
-
- 21 Jul, 2015 1 commit
-
-
Jacob Vosmaer authored
The existing behavior of the backups is to overwrite whatever data was still there in the scratch directories. This broke when we added a 'gzip' step because 'gzip database.sql' will fail if 'database.sql.gz' already exists. Doing 'rm -f database.sql.gz' before the 'gzip' avoids this failure.
-
- 07 Jul, 2015 1 commit
-
-
Jacob Vosmaer authored
We were using hacks to drop tables etc during a Postgres backup restore. With this change, we let pg_dump insert the DROP TABLE statements it needs at the start of the SQL dump.
-
- 06 Jul, 2015 2 commits
-
-
Jacob Vosmaer authored
This change helps system administrators who want to replicate GitLab backup files without needing root permissions.
-
Kamil Trzcinski authored
-
- 09 Jun, 2015 2 commits
-
-
Jeroen Nijhof authored
-
Jeroen Nijhof authored
-
- 02 Apr, 2015 1 commit
-
-
Valery Sizov authored
-
- 28 Mar, 2015 1 commit
-
-
Vinnie Okada authored
When creating backup tar files, only change permissions on the `db`, `uploads`, and `repositories` directories, not their contents.
-
- 25 Mar, 2015 1 commit
-
-
Vinnie Okada authored
-
- 20 Mar, 2015 1 commit
-
-
Vinnie Okada authored
-
- 19 Mar, 2015 1 commit
-
-
Administrator authored
-
- 18 Mar, 2015 1 commit
-
-
Vinnie Okada authored
Use more restrictive permissions for backup tar files and for the db, uploads, and repositories directories inside the tar files.
-