Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Install SubGit tool according to the Installation guide.

  2. Configure GitLab server:

    • Login to GitLab web GUI and create a new project:
      Image Removed
      Image Added

      Give a name to your projectdo not check “Initialize repository with a README” checkbox, and click Create project button.

      Image Removed


      Image Added

  3. Configure the repository:

    • Change identity to 'git' user:

      Code Block
      titlechange identity to git user
      $ su git

    • Change directory to that one that contains the newly created project. GitLab usually stores its project

      • Older versions of GitLab stored projects in

        No Format
      username here is actual GitLab username that was
      • where <username> was the GitLab username that had been used during the project creation on step 1

      . Step into that directory: Code Block
      titlechange directory
      $ cd
      • .

      • Since version 10.0 GitLab uses hashed storage as follows:

        No Format
      /userNew GitLab project that has been created at step 1 is being stored here in the directory of the same name we named the project
      • /@hashed/<hash[0..1]>/<hash[2..3]>/<hash>.git


        To find the repository path in GitLab v.10+, follow this guide

    • Navigate to that directory:

      Code Block
      titleNew project contentchange directory
      $ ls -l 
      total 0 
      drwxrwx---. 6 git git 131 apr 25 02:06 project.git 
      drwxrwx---. 6 git git 131 apr 25 02:06 /var/opt/gitlab/git-data/repositories/<repo_path>

    • Perform initial configuration:

      No Format
      $ subgit configure --layout auto --trunk TRUNK SVN_URL GIT_REPO


      • SVN_URL   – SVN project URL.
      • GIT_REPO  – a path to the new GitLab project that's been created at step 1, for example, project.git.
      • TRUNK     – a path, relative to SVN_URL, that leads to an SVN directory that plays a role of the main line of development.
      titlesee the configuration command example.

      Code Block
      titlesubgit configure example
      $ subgit configure --layout auto --trunk trunk ./project.git
                  SubGit version 3.2.4 ('Bobique') build #3670
                  Configuring writable Git mirror of remote Subversion repository:
                      Subversion repository URL :
                      Git repository location   : ./project.git
                  Git repository is served by GitLab, hooks will be installed into 'custom_hooks' directory.
                  Detecting peg location...
                  Authentication realm: <> Subversion Repository
                  Username [git]: user
                  Password for 'user':
                  Peg location detected: r10248 project/trunk
                  Fetching SVN history... Done.
                  Growing trees... Done.
                  Project origin detected: r1 project/trunk
                  Building branches layouts... Done.
                  Combing beards... Done.
                  Generating SVN to Git mapping... Done.
                  To complete SubGit installation do the following:
                  1) Adjust Subversion to Git branches mapping if necessary:
                  2) Define at least one Subversion credentials in default SubGit passwd file at:
                     OR configure SSH or SSL credentials in the [auth] section of:
                  3) Optionally, add custom authors mapping to the authors.txt file(s) at:
                  4) Run SubGit 'install' command:
                      subgit install ./project.git

    • Specify authors mapping.

      Configure authors mapping in default authors mapping file:

      No Format

      Or change core.authors option so that it points to the global authors mapping file.
      Find more details about authors mapping in Authors mapping article.

    • Specify a username and password that are used by SubGit to access the SCN repository. Edit passwd file:

      No Format

      By default, there's only subgit secret credential pair. Replace it with username and its corresponding password.

      titleSVN authentication

      There are several methods to configure authentication to access SVN server, but we use plain text password file here to simplify the guide. See more authentication methods in SVN Authentication if this method does not fit your needs.

  4. Establish mirror and start using new Git repository:

    • Establish two-way mirror by the command:

      No Format
      $ subgit install GIT_REPO


          GIT_REPO – a path to the GitLab project.

      titleSee SubGit install example…

      Code Block
      titlesubgit install
      $ subgit install ./project.git
        SubGit version 3.2.4 ('Bobique') build #3670
        Translating Subversion revisions to Git commits...
        Subversion revisions translated: 10248.
        Total time: 2 hours 15 minutes 24 seconds.

    • When the command completes, you can clone your new Git repository and start to work with it:

      No Format
      $ git clone GIT_REPO WORK_TREE


          WORK_TREE – a path to your working copy. 

      titleSee the command example

      Code Block
      titlerepository cloning example
      $ git clone /home/user/gitlab_project.git
        Cloning into '/home/user/gitlab_project.git'...
        Password for '': 
        remote: Counting objects: 99, done.
        remote: Compressing objects: 100% (39/39), done.
        remote: Total 99 (delta 50), reused 99 (delta 50)
        Unpacking objects: 100% (99/99), done.

      titleEmpty working tree case

      If Git warns you that you are cloning an empty repository and you don't see your files in the working tree, most probably automatic branches and tags mapping didn't work correctly. In this case, mapping has to be set manually, see details on mapping in Branches and tags mapping.

  5. Try and buy.

    titleTrial period

    Note: the trial period for SubGit mirror is 30 days, after that period you should buy a license key at

    Once you receive an email with a license key, upload this license key to your server and run the following command:

    No Format
    $ sudo subgit register --key subgit.key GIT_REPO


         GIT_REPO – a path to your newly created Git repository.

    titleSubgit register example…

    Code Block
    titlesubgit register
    $ sudo subgit register --key subgit.key /home/user/repo.git
       SubGit version 3.2.4 ('Bobique') build #3670
       Registration information:
         Registered for:       Example company
         Purchase ID:          OS-111111111111111
         Expiration date:      April 23, 2028
         You may use this key to register 9 more repositories (out of 10).
       Thank you for registering SubGit!
       Visit in case you have any questions and for more information on SubGit.

  6. Get support:

    Have you faced with any problems, see the following guide for more details: