Bug #4271

Browsing new repository groups via SVN issue

Added by Bert Zahniser almost 6 years ago. Updated almost 6 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Commit Number:
Affected Version:


When creating a new repository group and a new repository under that group, it is not available via an SVN connection until the apache2 service is reloaded/restarted. The group creation successfully updates the apache configuration file as outlined here:, but apache2 does not load the updated file until a reload/restart is issued. Can the server also reload the apache2 configuration when this file is changed?


Updated by Marcin Kuzminski [CTO] almost 6 years ago

  • Target version changed from v4.4 to v4.5

Hi Bert,

Yes this is a good improvement.

The plan should be:

  • add a new option called svn.proxy.reload_cmd
  • if that option is set execute it after generating the config
  • then users can set something like svn.proxy.reload_cmd = /etc/init.d/apache2 reload

we should make sure all error are nicely propagated to the logs from calling this command. That should allow to have a fully automated setup when handling subgroups in apache.


Updated by Martin Bornhold almost 6 years ago

  • Status changed from New to In Progress
  • Assignee set to Martin Bornhold

Updated by Marcin Kuzminski [CTO] almost 6 years ago

Note: as we discussed. Also a case when there's a new setup, and people don't add any repository groups can lead to template file not beeing created. We should expose a button in svn2apache config that allows to trigger an event, and create the generated file for use in SVN.


Updated by Redmine Integration almost 6 years ago

pullrequest created by martinb (status: under_review).


Updated by Martin Bornhold almost 6 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF