05 Aug, 2013
1 commit
03 Jun, 2013
1 commit
30 May, 2013
1 commit
-
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.
13 May, 2013
1 commit
-
Save backup time as is. Fixes #3857.
08 May, 2013
1 commit
06 May, 2013
1 commit
05 May, 2013
1 commit
23 Apr, 2013
1 commit
-
If the backup directory is not sub the gitlab install directory, then the git rev-parse call will fail.
18 Apr, 2013
1 commit
10 Apr, 2013
1 commit
05 Apr, 2013
2 commits
14 Mar, 2013
1 commit
-
Uses ActiveRecord::Base.connection.quote_table_name. Fixes issue 2437.
11 Feb, 2013
1 commit
05 Jan, 2013
1 commit
31 Dec, 2012
2 commits
23 Dec, 2012
1 commit
22 Dec, 2012
1 commit
20 Dec, 2012
2 commits
-
Rename gitlab:app:db_* to gitlab:backup:db:* Rename gitlab:app:repo_* to gitlab:backup:repo:* Rename *_dump to *_create
22 Nov, 2012
1 commit
-
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.
19 Nov, 2012
1 commit
26 Sep, 2012
1 commit
28 Aug, 2012
2 commits
-
New config option: git_hooks_path
26 Aug, 2012
1 commit
27 Jul, 2012
1 commit
26 Jul, 2012
1 commit
-
…ore 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).
18 Jul, 2012
1 commit
10 Jul, 2012
2 commits
