delta/gitlab/gitlab-ce.git/lib/backup, branch gitlab-flow gitlab.com: gitlab-org/gitlab-ce.git Backup wiki repo even if the main repo is empty 2014-05-08T20:50:48+00:00 Jacob Vosmaer contact@jacobvosmaer.nl 2014-05-08T20:49:27+00:00 0f29ccffd2b9805545db63d8266bb8367de1e35c This fixes a bug where wiki repositories for projects with an empty main repository would not get backed up. 
This fixes a bug where wiki repositories for projects with an empty main
repository would not get backed up.
Apply the locale encoding to `tar --version` 2014-05-08T16:23:44+00:00 Jacob Vosmaer contact@jacobvosmaer.nl 2014-05-08T09:02:04+00:00 da347d1bb45ad3b08b2aa0b40041c67dac0df3c5 Fixes a bug with non-UTF8 locales introduced by 2b816075dc71dfe8f6f9e5349fdff7f03ad9dad0. 
Fixes a bug with non-UTF8 locales introduced by
2b816075dc71dfe8f6f9e5349fdff7f03ad9dad0.
Use ProjectWiki instead of GollumWiki in code 2014-04-09T11:35:58+00:00 Dmitriy Zaporozhets dmitriy.zaporozhets@gmail.com 2014-04-09T11:35:58+00:00 1bd28994ccde18228a1c295110a283c79dfe70ee Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Drop all tables before restoring a PostgreSQL DB 2014-03-28T12:44:46+00:00 Jacob Vosmaer contact@jacobvosmaer.nl 2014-03-28T12:38:36+00:00 77b57c114be6b1fa02538c35066ccc363bfe68e6 Invoking 'db:schema:load' turned out to be a bad idea: when downgrading an existing GitLab installation, the schema of the newer version would be preserved when trying to import the old version. 
Invoking 'db:schema:load' turned out to be a bad idea: when downgrading
an existing GitLab installation, the schema of the newer version would
be preserved when trying to import the old version.
Replace backticks with Gitlab::Popen 2014-03-03T07:40:29+00:00 Jacob Vosmaer contact@jacobvosmaer.nl 2014-02-25T11:12:09+00:00 2b816075dc71dfe8f6f9e5349fdff7f03ad9dad0 






 Merge branch 'backup_uploads_symlink' into 'master'
2014-03-01T12:55:13+00:00

Dmitriy Zaporozhets
dmitriy.zaporozhets@gmail.com

2014-03-01T12:55:13+00:00

54e40241f6a61d0fae658501497bb5fb4e342989

Backup Uploads Symlink





Backup Uploads Symlink







Use Gitlab::VERSION to version backups
2014-02-27T13:30:41+00:00

Jacob Vosmaer
contact@jacobvosmaer.nl

2014-02-27T13:30:41+00:00

75f274b7505935cc5fd0b609a83afb1c8aaba79b

Previous to this commit, backups were tied to the git revision (SHA1) of
the app at the time the backup:create command was invoked. If the SHA1
at the time of restore was different, the script would refuse to restore
the backup.  This commit loosens this tie so that the backup script only
complains if the value of the Gitlab::VERSION constant is different
between the time of backup and the time of restore.





Previous to this commit, backups were tied to the git revision (SHA1) of
the app at the time the backup:create command was invoked. If the SHA1
at the time of restore was different, the script would refuse to restore
the backup.  This commit loosens this tie so that the backup script only
complains if the value of the Gitlab::VERSION constant is different
between the time of backup and the time of restore.







 Merge branch 'pg_force_restore' into 'master'
2014-02-27T12:27:30+00:00

Dmitriy Zaporozhets
dmitriy.zaporozhets@gmail.com

2014-02-27T12:27:30+00:00

0a963ee15a3c544fcf647ae94d348fe3369251c9

Pg Force Restore





Pg Force Restore







Empty the database during Postgres backup restore
2014-02-26T17:26:31+00:00

Jacob Vosmaer
contact@jacobvosmaer.nl

2014-02-26T17:26:31+00:00

8fe10e642ad9b5d236d2b00cea475bdc519130c0

The expected behavior during a GitLab backup restore is to overwrite
existing database data. This works for MySQL because the output of
mysqldump contains 'DROP TABLE IF EXISTS' statements. pg_dump on the
other hand assumes that one will restore into an empty database. When
this is not the case, during the restore with psql some of the data will
be skipped if existing data is 'in the way'. By first invoking `rake
db:schema:load` during a Postgres GitLab backup restore, we make sure
that all important data is correctly restored.





The expected behavior during a GitLab backup restore is to overwrite
existing database data. This works for MySQL because the output of
mysqldump contains 'DROP TABLE IF EXISTS' statements. pg_dump on the
other hand assumes that one will restore into an empty database. When
this is not the case, during the restore with psql some of the data will
be skipped if existing data is 'in the way'. By first invoking `rake
db:schema:load` during a Postgres GitLab backup restore, we make sure
that all important data is correctly restored.







Use gitlab_shell.path to invoke rewrite-hooks.sh
2014-02-26T16:32:52+00:00

Jacob Vosmaer
contact@jacobvosmaer.nl

2014-02-26T16:32:52+00:00

91c70c5b1c60160253520a5ac6ac3eec46faf416

The backup restore code for repositories was assuming that gitlab-shell
is installed in /home/git/gitlab-shell. This commit changes that to use
the configuration setting from gitlab.yml that specifies the path where
gitlab-shell is installed.





The backup restore code for repositories was assuming that gitlab-shell
is installed in /home/git/gitlab-shell. This commit changes that to use
the configuration setting from gitlab.yml that specifies the path where
gitlab-shell is installed.