[Template only, I am not the container author/maintainer]

 

Template: https://github.com/kilrah/unraid-docker-templates/blob/main/templates/subversion.xml

Source container: https://github.com/elleFlorio/svn-docker

Registry: https://hub.docker.com/r/elleflorio/svn-server/

 

An SVN server instance

This container may require some manual intervention in the console and/or appdata repository files regarding authentication, follow the instructions from:
https://medium.com/@elle.florio/the-svn-dockerization-84032e11d88d#.bafh3otmh

Edited October 26, 20223 yr by Kilrah

Hello,
I tried the alternative configuration via SVNADMIN but I have a problem because I don't know all the information I need to enter.
Can you help me ? or maybe you know a guide ?

Greetings Jama

I've never used svnadmin so can't help there, but did a test config using the instructions in the post I linked and that worked fine. 

Thanks for the answer.

Then how do you manage the users, groups and repository?

I have multiple users and multiple repositories, one of the users is leaving and new ones are joining.
Would like to manage it in the GUI.

Then I would have the groups and users under control.

I've always done it with Ubuntu and maintained the config files in the editor.

Unfortunately, I'm not very familiar with Docker yet, but I don't like running an additional VM on Unraid.

I've attached the picture, maybe you have an idea. (I wrote the text in red)

I think the Subversion authorization file must be different than the user authentication file (SVNUserFile) but I'm not sure what the path is.
Greetings Jama

okay I found the solution and would like to share it, now I understand a little better what docker means with the paths and executable.
Even if it says "The file does not exist." the command must be specified in this case. Now I can also create a repository before there were only error messages.

I hope this helps someone...sorry to bother Kilrah unnecessarily.

Greetings Jama

If you want them "correct" i.e. the full path you can check where those binaries are in the container by opening a console to the container and checking there. Also you'll probably want to copy the auth files to /home/svn so that they're stored in appdata on unraid side otherwise they'd be stored in the container and lost whenever it's updated.

 

 

There may be more steps needed to tell svn to use those though, don't have the time to look right now...

Edited September 22, 20223 yr by Kilrah

Hey guys so sorry but I am having a very hard time understanding how to set this up. I am used to using Visual SVN on a windows vm but honestly I dont want to keep running a full VM just for this... is there a step by step guide I can follow or can someone walk me thought it so I understand it?