You'll be prompted for credentials at this point ignore the prompt for Administrator credentials and press enter. Every good programmer always comments their source control actions, right?Įnter whatever comment you like, then save and close Notepad. It's a little weird when running locally on the server, as Subversion will pop up a copy of Notepad with a place for us to enter commit comments. Set SVN_EDITOR=c:windowssystem32notepad.exe Now let's verify that things are working locally by adding a root-level folder in source control for our new project, aptly named myproject.
This is easy enough to do through the traditional Windows services GUI. Normally, this is OK, but if you plan to implement any Subversion hook scripts later, you may want to switch the service identity to an Administrator account with more permissions. Note that the service is running under the Local System account. It's set to auto-start so it will start up automatically when the server is rebooted, but it's not running yet. Sc create svnserver binpath= "c:svnbinsvnserve.exe -service -r c:svnrepository"ĭisplayname= "Subversion" depend= Tcpip start= auto You can uncomment the default harry and sally users to play with, or add your own:Īs of Subversion 1.4, you can easily install Subversion as a Windows service, so it's always available. Next, add some users to the conf/passwd file. Within that newly created folder, uncomment the following lines in the conf/nf file by removing the pound character from the start of each line: Let's create our first source repository, which is effectively a system path. Note that the installer adds c:svnbin to your path, so you can launch a command prompt and start working with it immediately. I recommend overriding the default install path and going with something shorter: The first thing we'll do is download the latest Subversion Windows binary installer. It'll take all of 30 minutes, tops, I promise.
free?Īllow me to illustrate how straightforward it is to get a small Subversion server and client going on Windows. Beyond that, source control is source control, as long as you're not using Visual SourceSafe. I'm not necessarily advocating Subversion there are plenty of other great source control systems out there - but few can match the ubiquity and relative simplicity of Subversion. When it comes to readily available, free source control, I don't think you can do better than Subversion at the moment.
0 kommentar(er)
