- Install SubGit tool according to the Installation guide.
- Configure GitLab server:
- Log in to GitLab web GUI and create a new project:
Give a name to your project, do not check “Initialize repository with a README” checkbox, and click Create project button.
- Log in to GitLab web GUI and create a new project:
- Configure the repository:
Change identity to 'git' user:
change identity to git user$ su git
Change the directory to the one that contains the newly created project.
Older versions of GitLab stored projects in
/var/opt/gitlab/git-data/repositories/<username>
where <username> was the GitLab username that had been used during the project creation on step 1.
Since version 10.0 GitLab uses hashed storage as follows:
/var/opt/gitlab/git-data/repositories/@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:
change directory$ cd /var/opt/gitlab/git-data/repositories/<repo_path>
Perform initial configuration:
$ subgit configure --layout auto --trunk TRUNK SVN_URL GIT_REPO
where
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 toSVN_URL
, that leads to an SVN directory that plays the role of the main line of development.
Specify authors mapping.
Configure authors mapping in default authors mapping file:GIT_REPO/subgit/authors.txt
Or changecore.authors
option so that it points to the global authors mapping file.
Find more details about authors mapping in the Authors mapping article.Specify a username and password that are used by SubGit to access the SCN repository. Edit passwd file:
GIT_REPO/subgit/passwd
By default, there's only subgit secret credential pair. Replace it with the username and its corresponding password.
SVN authentication
There are several methods to configure authentication to access the SVN server, but we use a plain text password file here to simplify the guide. See more authentication methods in SVN Authentication if this method does not fit your needs.
- Establish a mirror and start using the new Git repository:
Establish a two-way mirror with this command:
$ subgit install GIT_REPO
where
GIT_REPO
– a path to the GitLab project.When the command completes, you can clone your new Git repository and start to work with it:
$ git clone GIT_REPO WORK_TREE
where
WORK_TREE
– a path to your working copy.Empty 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.
Try and buy.
Trial period
Note: the trial period for SubGit mirror is 30 days, after that period you should buy a license key at https://subgit.com/pricing.
Once you receive an email with a license key, upload this license key to your server and run the following command:
$ sudo subgit register --key subgit.key GIT_REPO
where
GIT_REPO
– a path to your newly created Git repository.- Get support:
If you encounter any problems, see the following guides for more details:
No license needed for import
Note: no license key required for import!
Should you need assistance, don't hesitate to contact us at support@tmatesoft.com.