Hi Florian,

The following conditions have to be met in order for this to work:

1. The Repository Web Service has been enabled and an API key was generated (cf. Administration > Settings > Repository)
2. Your server running OpenProject is configured to allow connections from the SVN server to the ‘/sys’ API endpoint.
3. Your SVN server runs Apache2 in order to use the included OpenProjectAuthentication.pm perl module.
4. The repositories you want to authorize through OpenProject are named identical to the surrounding project in OpenProject (e.g., project ‘Project with repository’ with an identifier ‘project-with-repository’. The repository must also be named ‘project-with-repository’ on your external SVN server.
5. Your SVN repositories are structured as follows:

• <SVN root directory (e.g. /opt/subversion/>
  • …

Then you can directly use the following guide regarding authorization of project repositories which is available at:
https://github.com/opf/openproject/blob/dev/doc/subversion_and_git_integration.md

You’ll need to change a few bits in that exemplary configuration, which is targeted at servers running OpenProject and mod_dav_svn on the same machine:

• Depending on your setup on the server that runs OpenProject, use LocationMatch to allow the SVN server access to the /sys API.
• Change the <Location /svn> to <Location />, as your message implies you’re using a subdomain for SVN.

Please reply to this post with any questions you might have regarding that configuration.

Best regards,
Oliver Günther

So finally, our external snv server is able to communicate with openproject.
Thanks Oliver for your effort, but your answer and the link was not useful.

In our case, the repository has a different name than the openproject project.
…and it works. ;-)

The problem I ran into, was that the history - or count of revisions - for this repository was to much for openproject.
So, the configuration was just fine, but after you click on repository insinde openproject a proxy error message appears after some time.
The result was, that openproject did not react anymore to any input.
After a restart, under the activity option, some revisions were added (but not all).
A tip from here https://community.openproject.org/topics/4943?r=5002 and here https://community.openproject.org/topics/4129?page=1&per_page=100 led me to the solution of setting the WEB_TIMEOUT parameter to 1000000.
After a long time and many timeouts and openproject restarts we finally have all revisions available in openproject for this repository/project.

After importing, I set WEB_TIMEOUT to a more normal value of 3600.
Now openproject works just fine and as expected.
I guess the same problem will appear if we try to add another existing large repository.

So, should I post a BUG?

Hi Florian,

thanks for the update! I will update the documentation with the specific project identifier requirement.
If you have other suggestions regarding improvements to the documentation (perhaps making it more visible at some other page), please let me know!

Concerning your follow-up issue:

Florian Seybold wrote:

I guess the same problem will appear if we try to add another existing large repository.

So, should I post a BUG?

If you can spare the time, a bug report from you would be awesome. I think we can find a way to work around that limit (e.g., by fetching the changesets asynchronously).
I will continue the discussion on that report.

Best,
Oliver