Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #3643

Closed
Open
Created Apr 19, 2013 by Administrator@rootOwner

Moving Gitlab 5.0 to a new server

Created by: AloysA

I've searched and found some old mini tutorials to move your gitlab to a new server. I'm currently using GitLab 5.0 and most of information is not applicable anymore. Can anybody point me in the right direction what I need to do? Afterwards I will summarize the steps I had to take.

Steps I already have taken:

  • Copy database to new server
  • Copy home/git/gitlab-satellites to new server
  • Copy home/git/repositories to new server (Don't forget to chown -R git ./home/git)

Things I learned (probably some things missing).

  • Take a look at the upgrade guide to your current version (so I looked at 4.2 -> 5.0). Because that guide assumes that you already have some data.
  • Create the database first with rake:setup , afterwards copy the data
  • Copy your authorized_keys file
  • I had to disable https certificate checking (Self signed certificate on the same machine, do not just do this).
  • Run gitlab-shell/support/rewrite_hooks.sh to fix your update and post_receive hooks
  • Use gitlab-shell/bin/check to check the gitlab-shell setup (most importantly the connection to gitlab)

As I said, probably a lot of stuff is missing, but this might help other people who will need to move their data to a new server. Everything is up and running now en a lot faster, so migrating is possible (without losing any data) :)

It would be nice if some official guide could be make. I think it is best to use the update guide to your current version., because that guide assumes you already have data.

Assignee
Assign to
Time tracking