2016-06-21 18:07:52 +00:00
|
|
|
# Project import/export
|
|
|
|
|
|
|
|
|
|
>**Note:**
|
|
|
|
|
- This feature was [introduced][ce-3050] in GitLab 8.9
|
|
|
|
|
- Importing will not be possible if the import instance version is lower
|
|
|
|
|
than that of the exporter.
|
2016-06-22 06:06:50 +00:00
|
|
|
- For existing installations, the project import option has to be enabled in
|
|
|
|
|
application settings (admin area).
|
2016-06-21 18:07:52 +00:00
|
|
|
|
|
|
|
|
The GitLab Import/Export version can be checked by using:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
# Omnibus installations
|
|
|
|
|
sudo gitlab-rake gitlab:import_export:version
|
|
|
|
|
|
|
|
|
|
# Installations from source
|
|
|
|
|
bundle exec rake gitlab:import_export:version RAILS_ENV=production
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
The current list of DB tables that will get exported can be listed by using:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
# Omnibus installations
|
|
|
|
|
sudo gitlab-rake gitlab:import_export:data
|
|
|
|
|
|
|
|
|
|
# Installations from source
|
|
|
|
|
bundle exec rake gitlab:import_export:data RAILS_ENV=production
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
[ce-3050]: https://gitlab.com/gitlab-org/gitlab-ce/issues/3050
|
