It seems that there may be more needed to make the SVN usable by clients.  I was following this but got stuck.  The first long command doesnt work - saying that aptitude is an unknown command.  Of the next thee things to do, only the first one works.  Without these, Im pretty sure the rest of the proceedure is doomed to fail.  At this junture - I seem well and truly stuck.

So if you wish to use aptitude (an alternative installer - similar to apt-get but with some nice features) then install it first:

apt-get install aptitude

Alternatively you could just use apt-get instead (replace aptitude with apt-get, also sudo is not required unless you aren't running as root. So the first line would look like this:

apt-get install libapache2-svn libapache-dbi-perl libapache2-mod-perl2 libdbd-mysql-perl libdigest-sha1-perl

See how you go now.

I personally don't want to manually enter in every User/Pass for svn access.  Namely because the password is plain text (and would be a lot cooler and more efficient if access can be controlled through redmine).

I have tried http://www.redmine.org/wiki/redmine/Repositories_access_control_with_apa...

but the svn apache config file isn't there.  I tried making a new conf file to see if it would work, but does not.  Would be great if someone can point me in the right direction.

We currently have to use a subscription (read: expensive) version of redmine because of this missing feature.  Please consider revising this - and including the automation/connection to the SVN.  We too have tried instructions to do it ourselves - to no avail.

Hello

I have my redmine working with svn (if i create a proyect the svn repo is created and the users are able lo login with the same credentials they use to login to redmine) 

If you tell me more details i can help you. Also the file you mention is dav_svn.conf? which distro are you using? I have it configured on debian, and that file is located in /etc/apache2/mods-enabled

Thats the file you should look and edit and of course, add it to the loaded modules of apache.

I was reading to see if this has been fixed in the distribution - or if these extra steps still need to be done afterwards?  I sure hope its been fixed.  :)

I finaly had time to check the latest release - what a wonderful distribution!

Sadly, the repositories are still not created automatically - the root concern of this thread still exists.  Has anyone a solution? I imagine a cron task would be the simplest way - I think thats how other distributions do it - but I dont know where to begin.

My first attempt with your suggestion didnt go perfectly, but progress WAS made.   Im doing a fresh install now to try again.  

After I installed the plugin, the svn was created using the new plugin (I saw the results in the filesystem), but Redmine didnt see the repo, and never displayed it as being there.

 I think I just didnt put the SVN/GIT folder where turnkey distro expected them to be.  Can anyone tell me where they should be placed for turnkey redmine webui to see them?

The plugin works to a point, but the SVN never show up in redmine webui.  This system is perfect - so close to be usable. Ill keep my fingers crossed that someone smarter than me will fix it.

But obviously not. I thought that may have been an easy workaround. Guess you'll have to try the original cron job suggestion as linked to above. The following post seems to have a revised cron entry.

And yes I think it'd be great if TKL could devise a way so this wasn't a problem, or at least was less of a problem.

Your comments are completely correct.  There seems to be no path to success with this release - and its a real shame.  Because this release isnt functional, we are foced to use an almost identical distribution that is a sibscription product.  The ONLY thing keeping us from using this version instead - is that it doesnt work. LOL.  We are real turnkey supporters, but nobody from turnkey ever answers this thread - and the situation for this hasnt changed in more than a year.  Most depressing.

Greetings all,

I've just joined the svn sufferers club :-(

The Redmine appliance itself looks nice, but it does not seem to be integrated with svn!

So I've just set up the svnserve in the very simple way, as explained in The SVN Book.

Edited  /srv/repos/<repo path>/conf/authz and passwd files. Entered svn user names and passwords manually. These can be different from Redmine credentials, but svn clients woud cache the repo URL with credentials anyway, they do not know a thing about the Redmine web interface.

Now I am able to access the demo svn project by URL: svn://<server>/svn/helloworld/trunk

It is obviously not perfect  - but much, much  better than nothing.

A question: the demo helloworld repo is defined with file:// protocol, while users obviously will access it thru svn:// Is this ok?  Should it be set to svn://localhost something?

Regards,

-- pa

Thanks this is useful. Exactly what I wanted: connect thru http instead of svnserve.  Will try.

But could you explain why to use ftp to upload files to the VM? Any problem with the webmin upload tool?

Regards,

-- pa