Commit graph

13 commits

Author SHA1 Message Date
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