Browsing new repository groups via SVN issue
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: https://docs.rhodecode.com/RhodeCode-Enterprise/release-notes/release-notes-4.3.0.html?highlight=svn, 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?
#1 Updated by Marcin Kuzminski [CTO] about 4 years ago
- Target version changed from v4.4 to v4.5
Yes this is a good improvement.
The plan should be:
- add a new option called
- 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.
#3 Updated by Marcin Kuzminski [CTO] about 4 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.
#4 Updated by Redmine Integration about 4 years ago
pullrequest created by martinb (status: under_review). https://internal-code.rhodecode.com/rhodecode-enterprise-ce/pull-request/2799
#5 Updated by Redmine Integration about 4 years ago
Commit 0a4f61937fe5 by Martin Bornhold email@example.com on default branch references this issue. https://internal-code.rhodecode.com/rhodecode-enterprise-ce/changeset/0a4f61937fe523c78feab73f1f0e480ac15116e6
#6 Updated by Redmine Integration about 4 years ago
pullrequest merged by marcink (status: approved). https://internal-code.rhodecode.com/rhodecode-enterprise-ce/pull-request/2799