summaryrefslogtreecommitdiff
path: root/lib/tasks/gitlab/backup.rake
Commit message (Collapse)AuthorAgeFilesLines
* Fixed backup.rake colorize method following Pages -> CEjej-fix-backup-rake-colorConnor Shea2017-02-071-6/+6
| | | Cherry-picked 'Remove colorize methods that weren't in CE.'
* Add GitLab PagesKamil Trzcinski2017-01-311-0/+21
| | | | | | | | | | | | | | | | - 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
* Fix: Backup restore doesn't clear cache12622-backup-restore-doesn-t-clear-cache-resulting-in-missing-branches-and-tagsValery Sizov2016-10-201-0/+2
|
* Fix restore warning messageDrew Blessing2016-06-281-1/+2
|
* Replace colorize gem with rainbow.Connor Shea2016-06-031-40/+40
| | | | | | | | | | | | | 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
* Fix backups if registry is disabledKamil Trzcinski2016-05-231-6/+14
|
* Added backup of container registryKamil Trzcinski2016-05-161-0/+21
|
* Reload the schema before restoring a database backupDrew Blessing2016-03-211-8/+26
|
* Backup LFS objects same as any upload.Marin Jankovski2015-11-191-0/+21
|
* Implement Build ArtifactsKamil Trzcinski2015-11-101-0/+21
| | | | | | | - Offloads uploading to GitLab Workhorse - Use /authorize request for fast uploading - Added backup recipes for artifacts - Support download acceleration using X-Sendfile
* Cleanup CI backup => migrate with GitLabKamil Trzcinski2015-09-151-0/+21
|
* Replace GITLAB with GitLab in rake task descriptionsDmitriy Zaporozhets2015-06-231-2/+2
|
* ability to skip some items in backupbackup_skip_optionValery Sizov2015-04-021-9/+24
|
* Explain why we create a StringIOJacob Vosmaer2014-11-201-0/+2
|
* Add CRON=1 backup setting for quiet backupsJacob Vosmaer2014-11-201-12/+23
|
* move backup logic to lib. Fixed removing outdated backupsDmitriy Zaporozhets2013-08-051-95/+7
|
* Correction to restore expected current directoryAngus MacArthur2013-06-031-9/+14
|
* fixes for gitlab restore with non-standard backup and repo dirsAngus MacArthur2013-05-301-0/+3
| | | | | | | | 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.
* Merge pull request #3858 from abalkin/issue-3857Dmitriy Zaporozhets2013-05-131-3/+4
|\ | | | | Save backup time as is. Fixes #3857.
| * Save backup time as is. Fixes #3857.Lev Abalkin2013-05-081-4/+3
| |
| * Save backup time as is. Fixes #3857.Lev Abalkin2013-05-061-3/+5
| |
* | Replace old hashes with new 1.9 ruby hashes (rebase)Andrey Kumanyaev2013-05-051-8/+8
|/
* fixed broken gitlab version determination during backupAngus MacArthur2013-04-231-2/+2
| | | | | If the backup directory is not sub the gitlab install directory, then the git rev-parse call will fail.
* Invoke shell setup after backup restoreDmitriy Zaporozhets2013-04-181-0/+1
|
* backup/restore uploadsDmitriy Zaporozhets2013-04-101-3/+19
|
* refactor backup/restoreDmitriy Zaporozhets2013-04-051-46/+7
|
* Replace db:backup/restore with native mysq/pg solutionDmitriy Zaporozhets2013-04-051-41/+6
|
* Adds DB-sensitive tablename escape for backup task.Chris Lawlor2013-03-141-1/+2
| | | | | Uses ActiveRecord::Base.connection.quote_table_name. Fixes issue 2437.
* No gitolite in project any moreDmitriy Zaporozhets2013-02-111-1/+1
|
* Fix backup/restore path_to_repoDmitriy Zaporozhets2013-01-051-2/+2
|
* Use project with namespace in email subjectDmitriy Zaporozhets2012-12-311-4/+4
|
* Fix backup/restore of reposDmitriy Zaporozhets2012-12-311-20/+34
|
* Update output of gitlab:backup:resoreRiyad Preukschas2012-12-231-35/+39
|
* Fix #2220v4.0.0rc2Dmitriy Zaporozhets2012-12-221-1/+1
|
* Rename gitlab:app:backup_* to gitlab:backup:*Riyad Preukschas2012-12-201-67/+71
| | | | | | Rename gitlab:app:db_* to gitlab:backup:db:* Rename gitlab:app:repo_* to gitlab:backup:repo:* Rename *_dump to *_create
* Update uses of Gitolite.config.foo settingsRiyad Preukschas2012-12-201-11/+11
|
* retrieve settings with symbolsHugo Duksis2012-11-191-3/+3
|
* cleanup rake tasksNihad Abbasov2012-09-261-25/+21
|
* Line not needed anymoreLeonB2012-08-281-2/+1
|
* Fixed some hardcoded pathsLeonB2012-08-281-0/+1
| | | | New config option: git_hooks_path
* No need to chown hooks in backup script any mroerandx2012-08-261-1/+0
|
* Post-receive hook should be owned by gitlab user, not git.Michael van Rooijen2012-07-271-2/+6
|
* Modified the `repo_dump` and `repo_restore` rake tasks to properly dump and ↵Michael van Rooijen2012-07-261-2/+4
| | | | 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).
* Fixing MySQL syntax errorMichael Richardson2012-07-181-1/+1
|
* Changes done as per feedbackStefan Morgenthaler2012-07-101-22/+15
|
* add: rake task to backup/restore gitlab db and reposStefan Morgenthaler2012-07-101-0/+197
View Lorry Controller Status