Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
619b30f6
Commit
619b30f6
authored
Feb 18, 2020
by
John Long
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update migrating between two self hosted instances
Change wording on migrating between 2 instances
parent
e8f51a55
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/user/project/import/index.md
doc/user/project/import/index.md
+2
-2
No files found.
doc/user/project/import/index.md
View file @
619b30f6
...
...
@@ -49,9 +49,9 @@ Docker pulls and pushes and re-run any CI pipelines to retrieve any build artifa
## Migrating between two self-hosted GitLab instances
The best method for migrating
a project
from one GitLab instance to another,
The best method for migrating from one GitLab instance to another,
perhaps from an old server to a new server for example, is to
[
back up the
project
](
../../../raketasks/backup_restore.md
)
,
[
back up the
instance
](
../../../raketasks/backup_restore.md
)
,
then restore it on the new server.
In the event of merging two GitLab instances together (for example, both instances have existing data on them and one can't be wiped),
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment