Reasons and solutions for various problems that SVN cannot connect to the server

Detailed explanation of SVN professional use tutorial

The first section installs the VisualSVN Server server

The first step is to download the SVN server. If you need a link, please send a private message.

 

 

Click the downloaded executable file to install

select components

Choose to install VisualSVN Server and Administration Tools components when deploying VisualSVN Server  .

Adjust the initial server configuration

Alternatively, adjust the default configuration settings before starting the installation. Select Standard Edition. Select the default port number and storage path.

 

 

Ready to install:

 

 

  • Location -- Specifies the VisualSVN Server installation directory. This option can only be configured during the first installation.
  • repository -- Specifies the root directory where the Subversion repository will be stored. For better performance, it is recommended to change the default location and store the repository on a non-system volume . However, you can keep the default repository location during the first installation and change it later through the VisualSVN Server Manager console.
  • Server Port -- Specifies the TCP port that the VisualSVN server will use for clients accessing the repository via HTTP(S). You can change the server port after installing the server.
  • Use secure connection -- Specifies whether to use the secure HTTPS protocol for client access to the repository. It is recommended to keep the HTTPS protocol enabled. You can adjust this option after installing the server.
  • backup -- Specifies the default destination for Subversion repository backups.

finish installation

On the last screen of the installation wizard, make sure the option to start VisualSVN Server Manager is selected . Click Finish to close the installer and continue with the server configuration steps using the VisualSVN Server Manager Console.

hint

As part of the installation process, VisualSVN Server configures and starts the VisualSVN Server service to make Subversion repositories available via the HTTP(S) protocol. If the service does not start during installation, please read article  KB29  for troubleshooting advice and advice.

Once the installation is complete, the VisualSVN Server Manager will start immediately. VisualSVN Server Manager is the main tool for controlling the server. The console provides an intuitive graphical interface for server and repository management.

Close the program, put the cracked file into the bin directory, click the Patch option, and execute the cracked file.

A dialog box pops up, indicating that the cracking is complete.

 

The installation is complete, open the software

Create repository file

create user

 

Set file properties

 

copy access path

https://20220723-093103/svn/myProject/

Then select the SVN client to log in on the computer another day.

Perform initial configuration

After completing the VisualSVN Server installation, you need to perform the initial server configuration and customize the new server deployment to your environment before the server goes live. The initial configuration process includes the following steps:

Configure network settings

 

VisualSVN Server provides several configurable network settings that you should review after installation and adjust as needed.

Follow the steps below to open network settings:

  1. Start the VisualSVN Server Manager console.
  2. Click Actions | Properties .
  3. Click on the Network tab.

  • name of server. By default, VisualSVN Server takes the local server hostname as the server name. If you plan to use another DNS name to access VisualSVN Server and the repository, you should manually adjust the settings to include this DNS name.
  • Automatically redirect HTTP to HTTPS (listens on port 80).  VisualSVN Server helps you transparently switch from plain HTTP to secure HTTPS protocol without any disruption to users. Consider enabling this setting if you plan to switch access to your repository from HTTP to HTTPS.
  • Repository URL. All repositories hosted on a VisualSVN server are nested under a single repository root in the URL. By default, the root URL prefix is ​​svn/. You can adjust the root URL prefix if desired.
  • Server binding. By default, VisualSVN server binds to all available IP interfaces. You can bind VisualSVN Server to a specific network interface if desired.

Read the article KB191: Understanding VisualSVN Server Network Settings for more information.

Configure user authentication settings

It is recommended to check the user authentication settings before starting to add a Subversion repository to a newly installed instance of VisualSVN Server.

 

Follow the steps below to open the authentication settings:

  1. Start the VisualSVN Server Manager console.
  2. Click Actions | Properties .
  3. Click the Authentication tab.

VisualSVN Server supports two different authentication modes:

  • Subversion authentication is suitable for non-domain VisualSVN Server installations with a small number of users. It relies on an internal user list maintained by VisualSVN Server and only supports basic authentication.
  • Windows Authentication works with VisualSVN Server installations in Active Directory. It relies on Active Directory user credentials and supports Basic Authentication and Integrated Windows Authentication (Active Directory Single Sign-On).

Read the article  KB182: VisualSVN Server Authentication Modes  for more information.

Configure SSL certificate

In order for end users to access the repository using the secure HTTPS protocol, the VisualSVN server must be equipped with a valid SSL certificate.

If you did not change the default settings during installation, your server should already be working on the HTTPS protocol, with an SSL certificate preconfigured for the hostname of the server machine where VisualSVN Server is installed. Depending on your environment and the options selected during installation, it will be a self-signed certificate or a certificate obtained from Active Directory Certificate Services (AD CS).

If the certificate was obtained from Active Directory and you did not change the server name on the Network tab , the certificate is already valid and trusted by clients from the appropriate Active Directory domain or forest. Therefore, no additional action is required.

In all other cases, see   the article KB134: Configuring SSL Certificates for VisualSVN Server .

add repository

A newly installed instance of VisualSVN Server does not contain any default repositories. You must create a new or import an existing Subversion repository into VisualSVN Server. VisualSVN Server Manager Console helps you add repositories in a straightforward wizard-driven mode.

Import an existing repository

To import an existing repository, run the Import Existing Repository Wizard in VisualSVN Server Manager :

  1. Start the VisualSVN Server Manager console.
  2. Right-click on the repository node.
  3. Click Import Existing Repository .
  4. Follow the steps of the wizard to complete the task.

For more information, read the article  KB10: Importing Repositories into VisualSVN Server .

When importing a repository with Subversion hook scripts, you should carefully test and check the hooks to make sure they work as expected on the new computer.

Create new repository

 

To create a new repository, run the Create New Repository Wizard in VisualSVN Server Manager :

  1. Start the VisualSVN Server Manager console.
  2. Right-click on the repository node.
  3. Click Create New Repository .
  4. Follow the steps of the wizard to complete the task.

Configure user permissions

VisualSVN Server allows you to specify initial user access rights when creating a new or importing an existing Subversion repository. Before the server goes live, it is recommended to check user permissions and adjust if necessary.

hint

You can allow non-administrator users to securely manage user access remotely. See the Enabling  Repository Administration Delegation section of this getting started guide for more details.

Server administrators and repository administrators must understand the principles of access control in Subversion. Read the article  KB33: Understanding VisualSVN Server Licensing  for more information.

VisualSVN Server fully supports path-based authorization with read/write, read-only and no access permission levels. You can manage user permissions at any level, including per-folder and per-file levels.

The VisualSVN Server Manager console provides an intuitive graphical interface for access control. You can define and manage user access without having to deal with command-line tools and text-based configuration files. What's more, VisualSVN Server allows you to automate access rights management and perform batch execution with the help of VisualSVN Server PowerShell.

Configure antivirus exclusions

During installation, VisualSVN Server automatically adds the necessary antivirus exclusions to the built-in Windows Defender antivirus. However, if you use other antivirus software, it is highly recommended that you add exclusions manually. Read  the KB171: Configuring antivirus exclusions for VisualSVN Server article for more information.

final check

At this point, the initial VisualSVN server configuration should be complete. Now is the time to perform a quick test drive to make sure the repository is online.

VisualSVN Server makes Subversion repositories available to users through the HTTP(S) protocol. To access data in the repository, you can use a web browser or a Subversion client, including command-line svn.exe and GUI clients.

When doing a quick trial, you should be logged into Windows with an account that has appropriate access to VisualSVN Server. If you have configured VisualSVN Server to use Integrated Windows Authentication, you will not be prompted for a username and password. You also shouldn't get warnings about untrusted SSL certificates.

subversion client test drive

The Subversion client is the primary tool for accessing and manipulating versioned data in a Subversion repository. As part of your final check, you should check your working copy with a Subversion client.

hint

We recommend using a modern and up-to-date Subversion client. If you prefer to use a graphical client, you can download  TortoiseSVN and install it on your workstation. TortoiseSVN is implemented as a Windows shell extension and provides a nice user interface for Subversion. You can download the latest TortoiseSVN version from the dedicated download page .

To access a repository, you should first fetch its URL. You can always find the correct repository URL using the VisualSVN Server Manager console:

  1. Start the VisualSVN Server Manager console.
  2. Expand the repository node.
  3. Right-click the repository or repository path and click Copy URL to Clipboard .

You can use the Ctrl+V keyboard shortcut to paste the URL into the Subversion client's URL field. If you use the command-line svn.exe  client, you should run the svn checkout command to create a working copy of the versioned project. Here is an example:

svn checkout https://svn.contoso.com/svn/MyProject/trunk MyWorkingCopy

Repository web interface trial

VisualSVN Server comes with a rich web interface for Subversion repositories. The web interface is automatically enabled for each repository hosted on a VisualSVN server.

As part of the final check, start your web browser and open the Repository Web Interface. To access a repository, you should first fetch its URL. You can always find the correct repository URL using the VisualSVN Server Manager console:

  1. Start the VisualSVN Server Manager console.
  2. Expand the repository node.
  3. Right-click the repository or repository path and click Copy URL to Clipboard .

After copying the URL, you can use the Ctrl+V  keyboard shortcut to paste it into your web browser's address bar and navigate to the repository.

Perform advanced configuration

VisualSVN Server offers additional unique features suitable for server installations of any size. These features are required for installing VisualSVN Server in an enterprise environment  .

Schedule repository verification

VisualSVN Server comes with built-in program validation for Subversion repositories. The verify job checks the integrity of the repository. Regularly validating your repository is important for early detection of repository corruption caused by disk failures. Read the article KB115: Getting Started with Repository Validation Jobs  for setup instructions.

Schedule repository backups

VisualSVN Server comes with a built-in backup and restore solution for Subversion repositories  . This feature helps you perform daily backups of repositories of any size without any impact on performance and user operations. What's more, the backup and restore features in VisualSVN Server are very easy to set up and maintain.

When deploying VisualSVN Server, we recommend that you add scheduled backup jobs to ensure your repository is properly backed up. Read the article  KB106: Getting Started with Backup and Restore  for setup instructions.

enable full text search

VisualSVN Server provides an almost zero-configuration full-text search solution for your repository   . Using this feature, all revisions in the repository can be indexed and searched through the web interface. Users can search for content, filename, and log message matches in any folder they have access to, filtering results based on authorization settings.

To start using full-text search, you need to enable search indexing in the server properties. Read article KB178:  Getting Started with Full-Text Search for Setup Instructions.

Enable submission email notifications

Commit email notifications are emails sent in response to new commits in the repository. VisualSVN Server can be configured to automatically send such email notifications for new commits in all or selected repositories. This can be achieved by using the Subversion hook handler included in the server installation package. Read the article  KB18: Configuring Email Notifications in VisualSVN Server  for setup instructions.

Enable access and operations logging

VisualSVN Server Essential and Enterprise licenses come with  access and action logging  . The access and operation logs allow you to monitor all HTTP requests and all logical Subversion operations processed by VisualSVN Server, including read-only operations such as Checkout and Update. You can use the Windows Event Viewer to view the logs, as log entries are recorded in the standard Windows event log.

Follow the steps below to enable access and action logging:

  1. Start the VisualSVN Server Manager console.
  2. Click Actions | Properties .
  3. Click the Logging tab.
  4. Select Access Logging and Operational Logging .
  5. Click Apply .

hint

By default, the maximum size of the Windows Event Log is 20480 KB, which may not be ideal for larger VisualSVN Server installations. It is recommended to review and increase the maximum log size depending on the load on the VisualSVN server. You can also adjust the event log retention policy. Follow the instructions in the following articles:

Enable delegation of repository administration

The VisualSVN Server Enterprise license comes with  the Repository Administration Delegation  feature. This feature helps you delegate user rights management responsibilities by assigning a repository supervisor - a non-administrative user who can manage user rights using the VisualSVN Repository Configurator tool. Read the article  KB62: Getting started with Repository Management Delegation  for setup instructions.

Enable multisite repository replication

VisualSVN Server Enterprise license comes with  multisite repository replication . This feature allows you to deploy replicated repositories at remote locations, enabling geographically distributed teams to use Subversion repositories at LAN speeds. Read the article  KB136: Getting Started with Multisite Repository Replication  for setup instructions.

Enable remote server management

The VisualSVN Server Enterprise license comes with  remote server administration  capabilities. The VisualSVN Server Manager console is implemented as a standard Microsoft Management Console (MMC) snap-in, allowing you to remotely manage multiple Subversion servers from a single console. Read the article  KB25: Configuring Remote Management  for setup instructions.

Guess you like

Origin blog.csdn.net/AQRSXIAO/article/details/129091143