- 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
-
- 28 Feb, 2017 1 commit
-
-
Jon Keys authored
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 21 Feb, 2017 1 commit
-
-
Drew Blessing authored
# This is the 1st commit message: Add `copy` backup strategy to combat file changed errors The backup Rake task used to stream data directly from the live data directory into the backup. Under many circumstances this worked OK. However, really active instances would experience a 'file changed as we read it' error - especially with data like the registry. This now copies the data first, then compresses it. It will take a bit more disk space while the backup is in progress, but it's a necessary thing. # The commit message #2 will be skipped: # Add env var
-
- 14 Feb, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 31 Jan, 2017 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
- The pages are created when build artifacts for `pages` job are uploaded - Pages serve the content under: http://group.pages.domain.com/project - Pages can be used to serve the group page, special project named as host: group.pages.domain.com - User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project - Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings - The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB) - The public/ is extracted from artifacts and content is served as static pages - Pages asynchronous worker use `dd` to limit the unpacked tar size - Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml - Pages are part of backups - Pages notify the deployment status using Commit Status API - Pages use a new sidekiq queue: pages - Pages use a separate nginx config which needs to be explicitly added
-
- 09 Jan, 2017 1 commit
-
-
Adam Niedzielski authored
-
- 07 Dec, 2016 1 commit
-
-
Sean McGivern authored
-
- 30 Nov, 2016 1 commit
-
-
David Gerő authored
-
- 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
-
- 10 Jun, 2016 1 commit
-
-
Stan Hu authored
Closes #12710
-
- 03 Jun, 2016 3 commits
-
-
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
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 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
-