Gosuke Miyashita
|
71ff619973
|
Fix hash key settings["gitlab_version"] to settings[:gitlab_version]
In backup_create, backup information hash is using symbol as its key.
But in backup_restore, string key is used and it returns empty value.
|
2012-11-22 10:38:56 +09: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 |
|