collective.recipe.rsync is a zc.buildout recipe that copies files between two locations via the rsync program.
Note
collective.recipe.rsync assumes you have a UNIX-based operating system and the rsync binary is in your PATH when you run Buildout or the rsync script.
Add a new section to your buildout.cfg file to use the collective.recipe.rsync recipe, e.g.:
[buildout] extends = https://raw.github.com/plock/pins/master/plone-4-3 parts += backup [backup] recipe = collective.recipe.rsync source = ${buildout:directory}/var/filestorage/Data.fs target = /var/backup
This copies a Plone Data.fs file from the source to the target.
Normally collective.recipe.rsync will run rsync during the recipe installation. Optionally you can create a script to execute rsync later by configuring the script = true option e.g.:
[backup] recipe = collective.recipe.rsync source = ${buildout:directory}/var/filestorage/Data.fs target = /var/backup script = true
This is useful in cases where you want to automate an rsync script with cron e.g. via z3c.recipe.usercrontab.
The default options are -av --partial --progress. Use the options parameter to change them e.g.:
[backup] recipe = collective.recipe.rsync source = ${buildout:directory}/var/filestorage/Data.fs target = /var/backup # Omit "-v" option options = -a --partial --progress
You can exclude files with the exclude option e.g.:
[backup] recipe = collective.recipe.rsync source = ${buildout:directory}/var/filestorage/Data.fs target = /var/backup exclude = Data.fs.index Data.fs.old
Optionally you may specify an alternate SSH port for rsync to use e.g.:
[backup] recipe = collective.recipe.rsync source = ${buildout:directory}/var/filestorage/Data.fs target = /var/backup port = 2222
- Support more than one script in the same buildout
- Generates bin/rsync script
- Disables rsync during buildout execution
- Facilitates creation of scheduled rsyncs via cron