Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7699903
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T22:35:15+00:00 2026-05-31T22:35:15+00:00

I have a working gitolite server. However, I want to move it to an

  • 0

I have a working gitolite server. However, I want to move it to an identical configuration, but on a bigger machine. Even though I have gitolite working, I am not sure about the strings under it. Mainly its relationship with ssh.

I would like to just install the packages gitolite, git-core. And move the repository directories for the git user. None of the keys need to change. Is this correct ? what are the configuration ties gitolite has to the current server. I am working with Ubuntu

I was specially confused by gl-setup, which did the job, but leaves me in the dark about the process.

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T22:35:17+00:00Added an answer on May 31, 2026 at 10:35 pm

    What you will need is also to move your ssh config:

    ~/.ssh/authorized_keys
    

    That is the file used by SSH and configured by Gitolite in order to:

    • list all the authorized public key
    • associated it with a forced-command script
    • pass the right user name to the gitolite script

    See "How Gitolite uses ssh"


    The OP confirms that was the issue and points out to the Gitolite documentation:
    "moving the whole thing from one server to another":
    (note: this is for ‘g2’; ie Gitolite V2, but the idea is the same for Gitolite V3 or ‘g3’)

    The idea behind this process is to create a new Gitolite instance, and then push your existing Gitolite repo, which will redeclare automatically all your current existing keys in your new server ~/.ssh authorized_keys for you.

    • install gitolite. Don’t worry about the pubkey used in the gl-setup step — for example this will do fine:

      ssh-keygen -q -N ” -f dummy
      gl-setup -q dummy.pub

    • edit the rc file to have similar settings to the old one.

    • Do not copy the entire file outright — some of the variables (notably GL_PACKAGE_CONF and GL_PACKAGE_HOOKS) are installation dependent and should not be touched!
      Do a diff or a vimdiff and copy across only what you know you changed on the old server.

    • disable the old server so your users will not push any changes to it.
      There are several ways to do this, but the simplest is to insert this line at the top of ~/.gitolite.rc on the old server:

      exit 1;

    • copy the contents of $REPO_BASE in the old server to $REPO_BASE on the new server.
      By default, as you know, these are both $HOME/repositories.

    • chown -R the files to the correct user if you copied using root.

    • fix up the hooks

      gl-setup

    • trigger a push to the admin repo

      git clone repositories/gitolite-admin.git /tmp/gitolite-admin
      cd /tmp/gitolite-admin
      git commit –allow-empty -m ‘trigger compile on new server’
      gl-admin-push -f

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a working Gitolite server right now and I backup every week. Now
using Gitolite on a Ubuntu server. Have a project im working on that i
I have working registration script the only problem is that i do not know
There are databases on Firebird and SQL Server. I have working stored procedure in
I have been working with SQL Server as a Developer a while. One thing
I have working solr-thumbnail in several parts of my project, but this time I
I have working code: [self performSelector:@selector(doSomething) ]; but when I change this line to:
i have working codes from my server which is really working using Xampp server
I am making a DOM builder which I have working succesfully but now I
I have everything working from the tutorial, replacing it with my data, but it

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.