Home
collective.recipe.rsync_datafs (0.1)
by
Olha Pelishok
—
last modified
2009-08-27
Released on 2009-08-27 by Alex Clark under LGPL - GNU Lesser General Public License available for All platforms.
Software development stage: stable
- collective.recipe.rsync_datafs download link: http://plone.org/products/collective.recipe.rsync_datafs/releases
- Homepage of collective.recipe.rsync_datafs: http://plone.org/products/collective.recipe.rsync_datafs
- collective.recipe.rsync_datafs repository: http://svn.plone.org/svn/collective/buildout/collective.recipe.rsync_datafs/
- Description source: http://pypi.python.org/pypi/collective.recipe.rsync_datafs
This recipe aims to formalize the common practice (for the author at least) of adding a part to a buildout to rsync data from production or staging to development for the purposes of demaking it easier to develop against 'real' data. It will accept username, source and target parameters then run rsync for you.
This is a simple zc.buildout recipe to to synchronize data from one place to another. Typically, it is used to transfer a Zope Data.fs file from production to development.
It assumes you have a UNIX-based operating system and that the rsync binary is in your path when you run buildout.
Supported options
The recipe supports the following options:
- source
- The source argument to pass to rsync, e.g. user@remotehost.com:/srv/client/var/filestorage/Data.fs
- target
- The destination argument to pass to rsync, e.g. ${buildout:directory}/var/filestorage/Data.fs
