On Wed, 2004-04-14 at 09:30, Marcin Kasperski wrote:
> Has anyone tried using subversion for backup and versioning Zope
> Data.fs files? How efficient is this?
That's funny. I *just* started teaching myself Zope over the weekend,
and was wondering about similar things: how does one version control a
Zope application?
According to a person I met in irc://irc.freenode.net/zope, he claims
that most Zope developers keep their main business-logic python code in
external version control, but that the internal database file is simply
backed up. (After all, Zope has its own internal version control on
objects.)
But the problem with this strategy, though, is that keeping only your
python code in SVN is incomplete. If my friend checks out the SVN
project, they have a bunch of code, but no idea how to arrange it within
a Zope tree... no templates, no data objects, nothing.
I've been wondering if it makes more sense to export an entire "Zope
folder" as XML, and keep that huge XML file (which contains everything:
python code, data objects, page templates, all directory structure) in a
Subversion repository.
> versioning Data.fs can mean scenario like: we have 50MB binary
> file, 500 times a day something appends new 50, 100 or 500 bytes
> at the end of it.
>
> How efficient can be commit in such a scenario?
Well, that means that 'svn commit' will only send the newly appended
data to the repository. And that same binary-diff will be used to store
successive revisions of Data.fs in the repository. The fact that
Data.fs is binary is irrelevant; Subversion treats all files and diffs
as binary.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 14 17:20:33 2004