• 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

    • For anyone looking for a lightweight formatting-free text editor, I recommend Notepad3.
    • This looks really dumb, especially if it costs $100+. Noone who cares about using a flight yoke would touch that thing, people who don't care are probably fine using the analog sticks on their controller, so who is it for?
    • A) "they shouldn't be making money off of those [free videos]"?? That is literally their business model, making money off videos that users post...if you don't feel like that should be allowed, then are you saying YouTube shouldn't exist. B) Yes, the example I gave is a net-negative transaction. If YouTube makes money from others who are following their rules, it doesn't change the fact that the person using an ad-blocker is costing them money. C) YouTube has always operated at a loss...kind of invalidates your entire argument. As I always say, I don't care what you do, I will not even say you are wrong for doing it. That is purely your choice. Just be honest enough to say something like "Google is rich, I honestly don't care." Perfectly fine reason. Don't act like there is some imagined justification for why it isn't breaking the rules.
    • You can now present content from your camera feed in Google Meet by David Uzondu Google has a new feature rolling out for Google Meet that lets you directly present video from an external camera feed right into your meetings. This means if you have a document camera for showing physical papers, a dedicated external camera for a better angle, or even output from a video production tool, you can now pipe that into Meet as a presentation source. This new option supports video up to 1080p at 30FPS. This "present from camera" function offers a more integrated way to handle certain video inputs compared to some existing workarounds. For instance, it might prove less complicated than a setup with OBS Studio where you arrange your various video sources into scenes, activate the virtual camera output, and then navigate Google Meet's settings to specifically choose "OBS Virtual Camera" as your video input before you can even start presenting that customized feed. Alongside this camera presentation feature, Google's announcement also mentioned several improvements to the general screen sharing experience in Meet. Initiating any type of screen share is faster now, and video quality during screen sharing has also been sharpened, with better handling of dynamic content like scrolling text or embedded videos. To reduce interruptions, if a second presenter stops sharing their screen, any previous presentation will now automatically resume. For those wondering when they can get their hands on this, the rollout for the camera presentation feature and these screen sharing enhancements has begun for Rapid Release domains. Users on Scheduled Release domains will start seeing it from June 11, 2025. Google notes that it could take up to 15 days for these features to be visible to all eligible users. Most Google Workspace accounts, including Business Standard and Plus, various Enterprise and Education tiers, and Workspace Individual subscribers, will have access. This new presentation option joins other recent Google Workspace enhancements. For instance, Gemini in Google Drive can now summarize changes to your files, offering a quick way to get updated on what you missed in documents since you last opened them.
  • Recent Achievements

    • First Post
      James courage Tabla earned a badge
      First Post
    • Reacting Well
      James courage Tabla earned a badge
      Reacting Well
    • Apprentice
      DarkShrunken went up a rank
      Apprentice
    • Dedicated
      CHUNWEI earned a badge
      Dedicated
    • Collaborator
      DarkShrunken earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      382
    2. 2
      +FloatingFatMan
      177
    3. 3
      ATLien_0
      174
    4. 4
      snowy owl
      169
    5. 5
      Xenon
      134
  • Tell a friend

    Love Neowin? Tell a friend!