• 0

Easy and simple guide to create a Subversion (SVN) server in Windows?


Question

Hey

Ive been literally killing myself looking up guides but most are way outdated and/or complicated. I tried a few simply ones but they simply appear to be out of date.

Can someone point me on a easy way to set it up in Windows? Ive been trying to use (as a client) TortoiseSVN but I simply cant get it to work. So I need something simply and easy.....

Thanks a lot!

18 answers to this question

Recommended Posts

  • 0
  On 02/04/2012 at 14:28, hjf288 said:

http://www.codinghor...on-windows.html

You need to run a server before you can connect using the client and its detailed on there

or use:

http://www.visualsvn.com/server/

Both look good. Im going to try the VisualSVN as the GUI way looks alot easier :p

Its for a Java project, but I perfer a generic version. Both of these look pretty generic so....

  • 0
  On 02/04/2012 at 14:28, hjf288 said:

A big +1 for VisualSVN; dead easy to configure and maintain yet still runs Apache at its core, plus it integrates nicely into the Microsoft Management Console so it can be administered very easily remotely as well. Can use SVN or Windows authentication. Depending on your needs though you don't even really need a server, TortoiseSVN can make a file based repository that can be on a network share faster than it took me to type that.

If you use Visual Studio, their client is quite good too. (Wraps around Tortoise.)

  • 0

Setting it up locally was pretty easy :)

Now the remote access is the hard part....

Lets say the url is: http://computernamehere.somelocaldomain.local:3980/svn/

How can someone access that from the outside? Thats what I cant really do.

On my internal LAN it works, but on the external I cant get it to work.

  • 0
  On 02/04/2012 at 15:05, htcz said:
On my internal LAN it works, but on the external I cant get it to work.

Will most likely need to add a port forwarding rule to your router.

  • 0
  On 02/04/2012 at 15:18, Max Norris said:

Will most likely need to add a port forwarding rule to your router.

Already done and nothing.

Like I said, I have a port forward rule for 8080 and that works. But it doesnt work for this (which is 3980) and it has a port forward rule too....

  • 0
  On 02/04/2012 at 15:22, htcz said:
Like I said, I have a port forward rule for 8080 and that works. But it doesnt work for this (which is 3980) and it has a port forward rule too....

Ahh thought you were mentioning your firewall, not the router. Are you using SSL? (Namely, forgetting to use https instead of http per your example URL above.)

  • 0
  On 02/04/2012 at 15:26, Max Norris said:

Ahh thought you were mentioning your firewall, not the router. Are you using SSL? (Namely, forgetting to use https instead of http per your example URL above.)

Well, no. But locally it works. Do I have to use SSL when accessing it on the outside?

  • 0
  On 02/04/2012 at 15:28, htcz said:
Well, no. But locally it works. Do I have to use SSL when accessing it on the outside?

No, just eliminating a possible issue. Is it hitting the server and being refused, or just not seeing it at all? (That is, an authentication issue.) Also, I just saw your example URL above, you can't access the repositories node using a subversion client, need the full repository path, for example: https://svn.example.com/svn/test/ You should also be able to access the web interface remotely. I'm using the default SSL port of 443, and it's working for me remotely anyway. Make sure you're adding the port number if you're going with a non-standard port.

Copy/pasting from VisualSVN's docs:

  Quote
Note Unlike web browsers, Subversion clients are unable to access the content of the Repositories node in the VisualSVN Server Manager. In other words, you are unable to access https://svn.example.com/svn/ URL using Subversion clients such as TortoiseSVN or svn.exe.
  • 0
  On 02/04/2012 at 15:36, Max Norris said:

No, just eliminating a possible issue. Is it hitting the server and being refused, or just not seeing it at all? (That is, an authentication issue.) Also, I just saw your example URL above, you can't access the repositories node using a subversion client, need the full repository path, for example: https://svn.example.com/svn/test/

Copy/pasting from VisualSVN's docs:

Not seeing it at all. Im using a web browser both locally and remotely.

Local side I access: http://computernamehere.somelocaldomain.local:3980/svn/

Remote side I access (if 234.11.23.12 was my WAN address): http://234.11.23.12:3980

  • 0
  On 02/04/2012 at 15:38, GreyWolf said:

Many ISPs block port 80 and 8080 and other "known" HTTP access points. It's possible that's why you cannot access it externally.

8080 isnt blocked by my ISP (a service I have on 8080 works remotely), and putting in my hosts file (if my web server address was hello.dev):

234.11.23.12 hello.dev

I am able to remotely access hello.dev

I dont think this is the only port that is blocked right? It would be too much of a coincidence.....

  • 0

OK, I finally got it to work (not my fault; damn dumbed down network admins :p )

Now, my next question is how do I access this thru a SVN client? In this fashion:

svn://234.11.23.12:3980

in TortoiseSVN doesnt work. Simply cant find it....

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I'm wondering if they are doing this as a "backup" in case CISA ceases to exist. It almost did recently due to funding and it's future is shaky. CISA - https://www.cisa.gov/known-exploited-vulnerabilities-catalog Example "CVE-2023-39780" https://www.cve.org/CVERecord?id=CVE-2023-39780 ASUS RT-AX55 Routers OS Command Injection Vulnerability
    • Over regulation is bad. That's why the EU is behind the US. But, it's a good thing the EU stepped in, in this case.
    • Thanks to the EU, Windows 11 is now a little more tolerable.
    • Microsoft will finally stop shoving Edge down your throat, on one condition by David Uzondu Avid Windows users must be familiar with the dirty tactics Microsoft employs to push its Edge browser. It's a song as old as time; remember when Internet Explorer was primarily used as a tool to download Chrome or Firefox because it was the only thing available? Shortly after IE died, Edge inherited that legacy, becoming the browser you often had to use just to get the browser you actually wanted. Even Microsoft knows this: For years, we have endured the relentless pop-ups after updates, third parties being blocked from changing the default browser on Windows 11, banners appearing when you dare visit a competitor's download page, a fake "how to uninstall Edge" guide, and links within Windows apps that just had to open in Edge, regardless of your set preferences. Microsoft has announced it is dialing back some of this aggressive behavior, promising a reprieve from the constant Edge bombardment. But (and it's a pretty big but) this only applies if you're in the EEA. This shift isn't Microsoft suddenly having a profound change of heart and deciding to respect user choice out of the goodness of its heart. No, this is all thanks to the Digital Markets Act, a major EU rule that targets big online platforms, what they call "gatekeepers", because these companies have a huge impact on how the digital market works. So, what is actually changing for users in the EEA? For starters, Microsoft Edge will not prompt you to set it as the default browser unless you actually open it directly, like by clicking its icon on the taskbar. This specific change started rolling out with Edge version 137.0.3296.52. Other Microsoft apps will also stop bugging you to reinstall Edge if you dared to remove it, with updates for this rolling out in June to Windows 10 and 11. And speaking of default browsers, this is where a significant improvement lies. Previously, hitting "Set default" for your browser in Windows was half baked, only grabbing basic web links like http and https and HTML files. Now, if you're in the EEA, setting your default browser will also cover more obscure link types like ftp and "read," plus a wider array of web-related file formats such as .mht, .svg, .xml, and even .pdf files, provided your chosen browser says it can handle them. The Bing app and those Windows Widgets, which previously had a nasty habit of ignoring your browser choice, will also start opening web links in your default browser. Hallelujah. Users in the EEA will also gain the ability to uninstall the Microsoft Store entirely later this year, though apps previously installed from it will still receive updates. Windows Search is also getting an upgrade in the EEA. Right now, searching from the taskbar mostly just sends you to Bing, no matter what browser you use. But for users in the EEA, other apps will be able to plug into Windows Search and show web results too. If an app registers as a web search provider, it'll start working as soon as you install it. You'll also be able to see results from multiple providers in the search interface, not just Bing. The usual scoping tabs will still be there if you want to filter things, but the default view will be more varied. And yes, you'll even be able to reorder the providers in Settings. These changes are already in Windows Insider builds and are expected to roll out to Windows 10 and 11 in early June.
  • Recent Achievements

    • One Year In
      WaynesWorld earned a badge
      One Year In
    • First Post
      chriskinney317 earned a badge
      First Post
    • Week One Done
      Nullun earned a badge
      Week One Done
    • First Post
      sultangris earned a badge
      First Post
    • Reacting Well
      sultangris earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      172
    2. 2
      ATLien_0
      125
    3. 3
      snowy owl
      123
    4. 4
      Xenon
      118
    5. 5
      +Edouard
      92
  • Tell a friend

    Love Neowin? Tell a friend!