Dmitriy Zaporozhets
b8f12d1917
Replace GITLAB with GitLab in rake task descriptions
2015-06-23 16:52:40 +02:00
Valery Sizov
67c83489ca
ability to skip some items in backup
2015-04-02 15:37:50 +03:00
Jacob Vosmaer
458f8c1f80
Explain why we create a StringIO
2014-11-20 15:54:39 +01:00
Jacob Vosmaer
7c54c63ac1
Add CRON=1 backup setting for quiet backups
2014-11-20 15:46:04 +01:00
Dmitriy Zaporozhets
02e859a234
move backup logic to lib. Fixed removing outdated backups
2013-08-05 12:26:33 +03:00
Angus MacArthur
5f4fea17ad
Correction to restore expected current directory
2013-06-03 11:00:24 -04:00
Angus MacArthur
9c82bca5ee
fixes for gitlab restore with non-standard backup and repo dirs
...
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.
2013-05-30 09:58:36 -04:00
Dmitriy Zaporozhets
e8b963fc32
Merge pull request #3858 from abalkin/issue-3857
...
Save backup time as is. Fixes #3857 .
2013-05-13 09:11:54 -07:00
Lev Abalkin
cef76fdd17
Save backup time as is. Fixes #3857 .
2013-05-08 16:42:29 -04:00
Lev Abalkin
7357ebc4a0
Save backup time as is. Fixes #3857 .
2013-05-06 19:58:10 -04:00
Andrey Kumanyaev
67ccc8b52a
Replace old hashes with new 1.9 ruby hashes (rebase)
2013-05-05 18:01:10 +04:00
Angus MacArthur
2ad723e1c1
fixed broken gitlab version determination during backup
...
If the backup directory is not sub the gitlab install directory,
then the git rev-parse call will fail.
2013-04-23 16:14:13 -04:00
Dmitriy Zaporozhets
a769662f18
Invoke shell setup after backup restore
2013-04-18 13:27:52 +03:00
Dmitriy Zaporozhets
e230551940
backup/restore uploads
2013-04-10 15:41:47 +03:00
Dmitriy Zaporozhets
c33d5e16fe
refactor backup/restore
2013-04-05 19:01:19 +03:00
Dmitriy Zaporozhets
38d23c0e5f
Replace db:backup/restore with native mysq/pg solution
2013-04-05 15:55:02 +03:00
Chris Lawlor
3df5253cc3
Adds DB-sensitive tablename escape for backup task.
...
Uses ActiveRecord::Base.connection.quote_table_name.
Fixes issue 2437.
2013-03-14 13:30:25 -04:00
Dmitriy Zaporozhets
d64090b8a9
No gitolite in project any more
2013-02-11 19:16:59 +02:00
Dmitriy Zaporozhets
2c8a46e0fe
Fix backup/restore path_to_repo
2013-01-05 23:29:48 +02:00
Dmitriy Zaporozhets
e5ff5c2869
Use project with namespace in email subject
2012-12-31 18:22:44 +02:00
Dmitriy Zaporozhets
8392449599
Fix backup/restore of repos
2012-12-31 12:01:05 +02:00
Riyad Preukschas
1b6c28b976
Update output of gitlab:backup:resore
2012-12-23 21:15:25 +01:00
Dmitriy Zaporozhets
988e6ac205
Fix #2220
2012-12-22 14:34:38 +02:00
Riyad Preukschas
c9bf2bb288
Rename gitlab:app:backup_* to gitlab:backup:*
...
Rename gitlab:app:db_* to gitlab:backup:db:*
Rename gitlab:app:repo_* to gitlab:backup:repo:*
Rename *_dump to *_create
2012-12-20 21:52:35 +01:00
Riyad Preukschas
19eb637419
Update uses of Gitolite.config.foo settings
2012-12-20 16:54:28 +01:00
Hugo Duksis
e7e1e99e92
retrieve settings with symbols
2012-11-19 22:42:58 +02:00
Nihad Abbasov
83696b127b
cleanup rake tasks
2012-09-26 04:18:10 -07:00
LeonB
ffdda12f66
Line not needed anymore
2012-08-28 14:18:49 +02:00
LeonB
c81d4ab4a9
Fixed some hardcoded paths
...
New config option: git_hooks_path
2012-08-28 10:57:23 +02:00
randx
867f46076e
No need to chown hooks in backup script any mroe
2012-08-26 01:40:01 +03:00
Michael van Rooijen
19f7b038cb
Post-receive hook should be owned by gitlab user, not git.
2012-07-27 15:30:36 +02:00
Michael van Rooijen
ec01cbef94
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).
2012-07-26 21:30:10 +02:00
Michael Richardson
0456ceddb4
Fixing MySQL syntax error
2012-07-18 11:59:32 +01:00
Stefan Morgenthaler
4dae41d5dc
Changes done as per feedback
2012-07-10 16:12:19 +02:00
Stefan Morgenthaler
12b34c8115
add: rake task to backup/restore gitlab db and repos
2012-07-10 00:01:05 +02:00