Jump to content

Recommended Posts

Apologies if anyone has been having trouble accessing the ICS SVN over the last week, I've retired the 12 year old VM it was running on and now installed SVN on a new hosted Windows Server 2019, not trivial since I'd forgotten how we set it up all those years ago and I've avoided messing with it so as not to break it.

 

But SVN is now running on a modern version of Apache supporting SSL and running on ports 80, 443 and 8443 (the old one), so you can access http://svn.overbyte.be/svn/ or https://svn.overbyte.be/svn/ as well as the old URL, or svn://svn.overbyte.be/ which is unchanged.  That last server took a long time to set-up because I thought it was part of Apache but turns out to be a little SvnServe program that had been running for 12 years without me noticing.  SVN is now also available on IPv6, but that is transparent and handled by DNS. 

 

I believe the Apache SSL configuration is correct, but it also serves svn.magsys.co.uk with a separate certificate and sometimes gets confused about which to send. 

 

Please shout if SVN does not behave as expected.

 

Angus

 

  • Like 1
  • Thanks 2

Share this post


Link to post

Awesome, at last I can forget that shaman dances to reach port 8443 through our corporative firewall

Share this post


Link to post

We all should thank Angus for his huge work in ICS world.

Angus, I say THANK YOU!

 

  • Like 2

Share this post


Link to post

Now trying to get the zips updated automatically, seems someone has been messing with SVN commands in the past 12 years, which is why I never updated anything!

 

Angus

Share this post


Link to post

Do you really want to check out the whole repository or only the trunk? If the former, this is correct, if the latter, add /trunk to the URL.

The result will then be a working copy that can be updated with

svn update

From within that directory.

Edited by dummzeuch

Share this post


Link to post

I would suggest to use TortoiseSVN which is a subversion GUI tool perfectly integrated in Windows Explorer context menu. Much easier to use than SVN command line.

 

In the command line, you should add usercode and password. Type "svn help co" to get help.

Usercode and password are both "ics" in lower case with quotes.

 

Try this command line:

svn checkout --username ics --password ics svn://svn.overbyte.be/ics/trunk

 

 

Share this post


Link to post

Hi Francios,

I am using Tortisesvn.

Thank you.  All good now.  Checked out Rev 1453

svn co --username "ics" --password "ics" svn://svn.overbyte.be/ics/trunk ics

Regards,

Ian

 

 

 

Share this post


Link to post

Does the server really use the svn: protocol? I thought that was legacy. Or does it use http(s)?

Share this post


Link to post
21 minutes ago, dummzeuch said:

Does the server really use the svn: protocol? I thought that was legacy. Or does it use http(s)?

I believe it serves both protocols as Angus said in #1

Share this post


Link to post

The server now uses all three protocols, svn, http and https.  The old server did not have https or rather we never set it up. 

 

I agree the svn protocol on port 3690 is very old, but we always supported it and many people will have scripts expecting to use svn (like me) rather than http, so it's still running. 

 

Angus

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×