This daemon uses pubsub to watch for both:
If either are detected, an updated asf-authorization and pit-authorization file will be generated in the directory specified as
output_dir in the svnauthz.yaml.erb template found in the subversion_server module.
This service uses the ASF's
pipservice Puppet class to operate and configure the daemon, and is deployed using the custom
Encrypted vars used to generate svnauthz.yaml from template are handled by and scoped for the
These values are defined in the encrypted nodefile for the host running the service.
This service runs as
www-data. The installation directory:
/opt/svnauthz and its contents are owned by
This service is deployed and runs as a systemd service unit.
systemctl (start|stop|status) pipservice-svnauthz.service
journalctl -u pipservice-svnauthz.service
In order to test changes to template files
/path/to/your/templates/(this will likely be
.../modules/subversion_server/files/authorization/; make sure the trailing slash is present and use the full path to the file, relative is not supported.)
refto hold “reference” outputs (call it anything and place it anywhere, it's just used to hold a pristine copy of the auth files as comparision.)
refdirectory, fetch the current/live set of authz files using
$ scp svn-master.apache.org:/x1/svn/authorization/*n .
$ ./authz.py --test(note the daemon will not start; the script will produce the authz files, then exit)
$ diff /tmp/authz/asf-authorization ref/
 The ‘check’ is currently just diffing the output, future may provide a syntax checker for validity.