GitLab

Created by: MatthieuBarthel

Hi,

The backup rake task is really useful, but I'm having an error that I don't understand. When I set up the backup_path outside the gitlab repo (here /home/gitlab/backup), I get the following result :

gitlab@imatt:~/gitlab$ bundle exec rake gitlab:app:backup_create RAILS_ENV=production
Dumping database tables:
- Dumping table events... [DONE]
- Dumping table issues... [DONE]
- Dumping table keys... [DONE]
- Dumping table merge_requests... [DONE]
- Dumping table milestones... [DONE]
- Dumping table notes... [DONE]
- Dumping table projects... [DONE]
- Dumping table protected_branches... [DONE]
- Dumping table schema_migrations... [DONE]
- Dumping table snippets... [DONE]
- Dumping table taggings... [DONE]
- Dumping table tags... [DONE]
- Dumping table users... [DONE]
- Dumping table users_projects... [DONE]
- Dumping table web_hooks... [DONE]
- Dumping table wikis... [DONE]
Dumping repositories:
- Dumping repository iMatt... [DONE]
- Dumping repository NRJ... [DONE]
- Dumping repository Attrib-Next... [DONE]
- Dumping repository Attrib... [DONE]
- Dumping repository Fit-Form... [DONE]
- Dumping repository gitolite-admin.git... [DONE]
fatal: Not a git repository (or any of the parent directories): .git      # error here
Creating backup archive: 1343403705_gitlab_backup.tar [DONE]
Deletion of tmp directories...[DONE]
Deleting old backups... [DONE]

I have an additional error if the backup_path is on another disk (here a backup disk in /srv/disk_name/gitlab) :

Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

In both cases, the backup archive is well created and it has the exactly same size that a backup without error that I would have made on Rails.root + backups.

Thanks a lot for the awesome work :)