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

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

CORS support from WSO2 API Manager 2.0.0

Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources  on a web page to be requested from another domain outside the domain from which the first restricted resource was served. For example, an HTML page of a web application served from http://domain-a.com makes an <img src >  request for a different domain as 'domain-b.com' to get an image via an API request.  For security reasons, browsers restrict cross-origin HTTP requests initiated from within scripts as in above example and only allows to make HTTP requests to its own domain. To avoid this limitation modern browsers have been used CORS standard to allow cross domain requests. Modern browsers use CORS in an API container - such as  XMLHttpRequest  or Fetch - to mitigate risks of cross-origin HTTP requests.Thing to  note is it's not only sufficient that the browsers handle client side of cross-origin sharing,but also the servers from which these resources getting need to handl

[WSO2 AM] APIStore User Signup as an approval process

In previous versions of WSO2 APIManager before 1.6.0, it was allowed any user who's accessible the running APIStore come and register to the app.But there will be requirement like,without allowing any user to signup by him/her self alone,first get an approve by a privileged user and then allow to complete app registration.Same requirement can be apply to application creation and subscription creation as well.To fulfill that,we have introduced workflow extension support for  WSO2 APIManager  and you can find the introductory post on this feature from my previous blog post on " workflow-extentions-with-wso2-am-160 " . From this blog-post,I'll explain how to achieve simple workflow integration with default shipped resources with  WSO2 APIManager 1.6.0 and WSO2 Business Process Server 3.1.0 with targeting "user-signup" process. Steps First download the WSO2 APIManager 1.6.0[AM] binary pack from product download page . Extract it and navigate to