Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Access methods to a Subversion repository

SubGit, like any other Subversion client, can access a Subversion repository by using one of the following protocols.

Table 1. Subversion repository access protocols

ProtocolAccess Method
Direct repository access.
Access via custom protocol to the svnserve server.
Same as svn://, but through an SSH tunnel.
Access through a web server (usually Apache)
with possible SSL encryption.

The access via file:// can be used when both Subversion and Git repositories are hosted on the same machine. In this case, the local operating system account is used for authentication and no additional settings are required.

All the other access methods to a Subversion repository require the appropriate authentication settings for SubGit.

Obtaining the authentication data for a Subversion repository

SubGit obtains the authentication data from the [auth default] section of the SubGit configuration  file that is located at GIT_REPO/subgit/config.

Depending on the configuration, your Subversion server can request the following authentication  data to log in to a Subversion repository:

  • a username and a password
  • an SSL client certificate
  • an SSH private key

In the [auth "default"] section of the SubGit configuration file, you can specify the authentication settings depending on the authentication data that is required to log in to a Subversion repository.

  • No labels