subversion configuration

Got it! Edited the file within vi (yuck!) under SSH.

1 thing I couldn't do was enable the service to auto start, the error I got back is:

root@ReadyNAS2:/etc/systemd/system# systemctl enable svnserve.service
Failed to issue method call: Invalid argument

Good to hear that you got a step further. These system files aren't shared via SMB, so you need direct access to edit them as you did with vi.
On Windows WinSCP is a great tool for such things that makes browsing the file system and editing files very easy, but as the name suggest, it's only for Windows.
Don't know if there are similar tools for Mac.

OK, regarding your error message. It's a bit vague, don't know what "invalid argument" means. Maybe double check that your svnserve.service file contais the above contents. Or maybe check the permissions:

root@readynas:~# ls -l /etc/systemd/system/svnserve.service
-rw-r--r-- 1 root root 224 Feb 14  2014 /etc/systemd/system/svnserve.service

HOWTO:

This is how I got subversion running on my brand new 314, running stock 6.2.2.

Step 1. Install the subversion app.

This is non trivial because the installation through Frontview seems to be broken (please Netgear how about a check and fix?)

To install it I eventually was able to find (google it) the subversion for readynas OS subversion-ntgr.deb file. Download that, and then use the upload button in frontview to install it.

This will install subversion, but leaves you in the dark as to what to do next. Presumably it could work using the svn: access method, but I want http and https:.

Step 2. Install the missing modules into the web server.

Using SSH login, issue the commands:

apt-get update
apt-get install libapache2-svn

This will download and install mod_dav_svn.so and (although it does not seem to be used or needed... but might depending on access / authentication that you want to use) mod_authz_svn.so.

At this point you are not much further advanced because you need a place for your subversion repository, and a means of pointing the web server at it.

Hence:

Step 3. Make a place for your subversion repositories.

I created mine under /data/.svn

In there I have created htpasswd-file (the authentication password file), and a directory called repos.

under repos, are each of the subversion repositories.

DO NOT make a share through Frontview for the repository location. You DO NOT want to have SMB / NFS / AFS access into the gory guts of the repository, and you don't want standard web access to it either.

Step 4. Tell the web server how to get into the repository.


You need to have a ".conf" file for the web server so that it can figure out the map from a URL to the underlying storage.

NORMALLY, on OS6, it looks like there should be a file under /apps which is the http web server configuration for each app. However there is no such file for the subversion app, and if you made one it would not be used because there is another file which references them all, and it is auto-managed by Frontview (so edits would get eaten). So instead we create a new file in the global apache2 configuration files location.

So, make a new file called SUBVERSION.conf, and create this in /etc/apache/conf.d

In this file, I put this content:

LoadModule authn_default_module /usr/lib/apache2/modules/mod_authn_default.so

<Location /svn/>
DAV svn
SVNParentPath "/data/.svn/repos"

SVNListParentPath On

AuthType Basic
AuthBasicProvider file
AuthName "Source Repository"
AuthUserFile "/data/.svn/htpasswd-file"
Require valid-user
</Location>

Step 5. Make sure you have a valid username and password in you htpasswd-file (Mr Google will help out there).

A few commands will sort that out.

Step 6. Restart the web server.


systemctl restart apache2

Now, point your browser at your nas thus:

http://mynas/svn/

Where "mynas" is the name of your NAS.

You should be prompted for the username and password set up in the htpassword-file above, and when that is entered correctly, you should be able to see and browse the subversion repositories.

Step 7. Niceties


If your NAS is to use port forwarding through the public internet, then forwarding port 80 will show anyone who comes along that you have a readynas there. They will have to use your admin usename and password, but the less you show the better.

So make a new share called something like "webroot", make that the HTTP default, and in that make a file called "index.html". In that file, just enter some text like "Access Denied", save it, and then anyone who casually points a web browser at your NAS (on port 80) gets that message. They, and you, have to use https://yournas/admin to get the admin page.

Hi quickly_now, thank you for your step by step guide!

Unfortunately I can't open the URL in step 6. The restart of the web server worked (once I fixed the SUBVERSION.conf script due to a copy paste error on my part).
I cannot see anything obvious wrong, I went through all the steps and they appeared to succeed, but the URL (using my nas server name) never returns and so I don't get asked for a username and password (which I generated with one of the various htpasswd generator websites).

Any pointers at what I should check?

EDIT: also I realised the path you suggested for SUBVERSION.conf was incorrect, it should be:

/etc/apache2/conf.d

Cheers
John

Hello Everyone,

I've had the ReadyNas 314 with 8TB for a while now but still have not managed to set up SVN.

This is my first ever NAS.

I wanted to set up version control for personal programming projects.

I have looked at the guides above and this one http://www.readynas.com/forum/viewtopic.php?f=35&t=19839 however I still haven't managed to get anywhere.

Please can someone guide me to some detailed instructions of how to set up, install, and basic use/demo.

(Sorry if post is in the wrong place)

Regards