You can define supergroups from LDAP groups safely. All text found "around" the auto-generated groups are now restored at the right place.New parameter -n to keep exact LDAP group names.Hard-coded parameters at the top of the script are now optional.Exit with error code 1 when no group is found.New parameter -v to distinguish warning/error and info verbosity (-v enables info logs -q disables warning/error logs).Better management of outputs: all errors/warnings are directed to stderr info messages are given to stdout if an authz destination file is provided and are redirected to stderr otherwise.(I wrote this when my Python kung fu was not all that great and it shows somewhat.) Change Log I do hope to spend some time on this project to get it rewritten not only to address the bugs reported but also to clean things up. (During the migration I changed the license from GPLv3 to MIT.) My hope is that this will simplify the involvement of the community. At the request of the community members I have moved this project from BitBucket to GitHub. For WebDAV proxy configuration, see the WebDAV proxy documentation.This script was written almost 10 years ago and has been barely maintained. The article using svnsync gives more hands-on information. The svnsync documentation is minimal but enough for a quick start. The page How to setup SSH without password (one out of many) explains how to add a non-password login with ssh. Obviously ssh must be configured in a way not to ask the password. Ssh -l svnsync "/path/to/svn-sync-slave.sh -r /path/to/local/repository" We can do this easily by editing the post-commit hook script on the master repository. We need thus a mechanism to trigger the replication from the master to the slave server. Strictly speaking, no configuration is needed on the server to allow the slave to mirror a repository, but as soon as data is committed on the server, the slave's repository will get more and more out of date. The master server must run subversion 1.4 or higher in order to provide support for svnsync. The operations described in this section can be performed by the mighty SVN slave sync script. Svn pdel -revprop -r 0 svn:sync-lock file:///path/to/local/repository Please be aware that you can seriously screw your repository up if you delete the lock while svnsync is running! Should the synchronisation fail and leave the repository locked, then the following line deletes. Svnsync sync file:///path/to/local/repository Once the repository is initialised, further updates need only the minimal command line: Svnsync init -username svnsync file:///path/to/local/repository \ The slave repository is initialised by the following command line: Let's make it executable with the following command and we're ready to go.Ĭhmod x /path/to/local/repository/hooks/pre-revprop-change Svnadmin create /path/to/local/repositoryĬhown svnsync: /path/to/local/repository -Rīefore svnsync update the data from the server, we have to manually create the file /path/to/local/repository/hooks/pre-revprop-change with the following content:Įcho >
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |