Skip to main content

Installing SVN on Windows



Install SVN Server

The steps to install SVN on windows as a service are listed below.

Download the latest Subversion Windows binary installer from svn windows binary installer download. At the time of writing, that's 1.67. Then install it. (It’s better to override the default install path and going with something shorter as C:\svn\).

The SVN installer adds c:\svn\bin to the installation path and can launch a command prompt and start working with it immediately.

Then create the first source repository using following command.

svnadmin create "C:\svn\repository"

Within that newly created ‘repository’ folder, uncomment the following lines in the conf/svnserve.conf file by removing the pound character from the start of each line:
anon-access=none

auth-access=write

password-db=passwd

Next, add some users to the conf/passwd file. Uncomment the default harry and sally users to play with, or add own users:
harry=harryssecret

sally=sallyssecret

Then to install Subversion as a Windows service issue the following command:
sc create svnserver binpath=”c:\svn\svnserve.exe --service –r c:\svn\repository”

displayname=”Subversion” depend=Tcpip start=auto


It's set to auto-start so it will start up automatically when the server is rebooted, but it's not running yet. To fix that,issue the following command:

net start svnserver

Access SVN Server by clients

Most people use TortoiseSVN to interact with Subversion. Download the latest 32-bit or 64-bit Windows client (1.6.7 as of this writing) from http://tortoisesvn.net/downloads and install it.

svn:// is specified as the prefix to our source control path, which means we're using the native Subversion protocol. The Subversion protocol operates on TCP port 3690.

So as an example you can access your SVN repository by typing following url in IE browser;
svn://localhost/yourRepositoryName/

Comments

Post a Comment

Popular posts from this blog

Convert an InputStream to XML

For that we can use DocumentBuilder class in java. By using the method parse(InputStream) ; A new DOM Document object will return. InputStream input; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); DocumentBuilder parser = factory.newDocumentBuilder(); Document dc= parser.parse(input); In the above code segment,by using the created Document object,the corresponding XML file for the inputStream can be accessed. References: http://www.w3schools.com/dom/dom_intro.asp http:// download.oracle.com/javase/1.4.2/docs/api/javax/xml/parsers/DocumentBuilder.html
2 comments
Read more

Concat two xml values with XSLT

The use-case described in this blog-post,is there's an WSO2 ESB node setup to proxy an incoming message to a particular back-end endpoint.  Before delivering the message to the back-end endpoint,from the ESB node itself,this incoming message need to processed and change its inside xml payload format. For eg: Below is the incoming message <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"> <OwnerData> <Name>John Smith</Name> <openedDate>12/12/80</openedDate> <quality>good</quality> </OwnerData> <CinemaHallData> <rows>100</rows> <seats> <seat>50</seat> <seat>60</seat> </seats> </CinemaHallData> </CinemaHall> This message need to be changed as  below; <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"...
3 comments
Read more

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage  as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...
7 comments
Read more