subversion configuration

I found the downloadable virtual machine, which enabled me to tinker freely without fear of breaking anything significant ;)

edit: after more reading, I think my instructions are very strange ;) better not use these yet...

Hi,

AFAIK, for SVN HTTP(S) access the apache modules "mod_dav_svn.so" and "mod_authz_svn.so" are missing. I think these should be provided by the subversion app.
Anyway, I just installed the svnserve (SVN://) method, to get at least any kind of subversion:

• Select a place for the SVN repositories. I just created a share 'svn' from frontview for this. This is located at /data/svn. Probably best to don't make it accessible by any network protocol.


• Create a SVN repository, I called it "projects". Rename it as you like.
  

  svnadmin create /data/svn/projects



• Optionally, edit /data/svn/projects/conf/svnserve.conf. I disabled anonymous access completely:
  

  
      [general]
      anon-access = none
      auth-access = write
      password-db = passwd
  



• Edit /data/svn/projects/conf/passwd
  Add usernames and passwords as desired.
  


• Create /etc/systemd/system/svnserve.service
  

  
      [Unit]
      Description=SVN Server
      After=network.target
      
      [Service]
      Type=forking
      PIDFile=/run/svnserve.pid
      ExecStart=/usr/bin/svnserve -d -r /data/svn/ --pid-file /run/svnserve.pid
      
      [Install]
      WantedBy=multi-user.target
  



• Start the SVN service with:
  

  systemctl start svnserve.service



• If the above worked correctly you can install the service so that it starts automatically on bootup:
  

  systemctl enable svnserve.service

The SVN server should now be available at svn://<your nas address>/projects (or the name you gave your repository).

Disclaimer: I'm no Linux expert and this might not be the best/safest/whatever approach, but it works for me. Feel free to make suggestions for improvement!

twinpeaks

Hello,

Thanks for your information for setting up an svn. I followed your steps and was able to create one successfully. However, now I'm encountering an authorization failed message when attempting to commit to the repository. Do you, or anyone know how to solve this issue? I believe the issue is because I put the svn server repo directory into the /data/svn/ share, and when I try to connect with the svn user it's failing because it is expecting a valid user associated with my NAS, not the svn user. I'm not sure. I do however never get a prompt to login with a username or password.

Any clarification and insight into solving this issue would be greatly appreciated.

[EDIT]
I found the fix, it seems.

In the svnserve.conf file, just make sure the # symbols (comments) are removed before the:
anon-access = none
auth-access = write
password-db = passwd

Hi,

I'm trying to get subversion running on my RN104. I think I have everything setup, however I think I am missing the modules for apache here:

AFAIK, for SVN HTTP(S) access the apache modules "mod_dav_svn.so" and "mod_authz_svn.so" are missing. I think these should be provided by the subversion app.

How do I get these modules? I installed the app, but I don't see these modules anywhere.

Any help would be greatly appreciated.

Thanks,
Cory

Thanks! This post helped me get my SVN up and running

Please can someone post a step by step guide for newbie? I have problem after the installation (I get some error here: Start the SVN service with:
systemctl start svnserve.service) my subversion still doesn't work and I don't know how to resolve.
Thank you

I too am somewhat stuck here, I have svn installed, enabled ssh and have created the projects repo as mentioned, but I cannot connect to it or browse to it.
Where does svn keep its own configuration? I created the svn share in data, the repo I created is in data\svn\projects
The example above talks about creating a service in the etc folder, that doesn't exist on my 104.

I can only speak for my RN102. The above steps were all I did to set up SVN. I can't remember under which firmware version I did the install, but it was the current version back then. I keep the FW always up-to-date, so now I have 6.2.2 and SVN is still running OK.
Are you sure that you don't have the /etc folder? What's the output of this command?

ls /

What firmware are you running?

Hi TwinPeaks! Sorry for the tardy response, thought I would have got a notification that you replied, silly me I didn't tick the box.

Ok, Im running 6.2.2 according to the 104 admin page.
ls / does show an etc folder:
apps data frontview lost+found opt run srv usr
bin dev home media proc sbin sys var
boot etc lib mnt root selinux tmp

but I cannot see the etc folder when I navigate to the NAS. Im using a Mac, and browsing to the NAS via SMB and AFP.
I can see my shares, and the hidden folders in the data directory (like .apps) but I cannot see an etc folder anywhere. :(

EDIT: Updated with the full output of ls

Navigating to the NAS via my windows VM, I still cannot see the etc folder. Im browsing as the admin user btw.