I've finally reached the point where the site code base is large enough that weve managed to create a version problem. <sigh> It's time to put the whole thing under source code verison control. I don't see the best way to do this in the Zope enviroment, at least not transparently. (For example, downloading with FTP and uploading is not invarient.) What's the preferred approach?
On Mon, Aug 26, 2002 at 10:51:30PM -0700, Dennis Allison wrote:
I've finally reached the point where the site code base is large enough that weve managed to create a version problem. <sigh> It's time to put the whole thing under source code verison control.
I don't see the best way to do this in the Zope enviroment, at least not transparently. (For example, downloading with FTP and uploading is not invarient.) What's the preferred approach?
Just a thought: You could use Filesystem Directory Views instead of Folders. Then you could use CVS on the filesystem, but you'd lose through-the-web editing. --PW Paul Winkler "Welcome to Muppet Labs, where the future is made - today!"
On Mon, Aug 26, 2002 at 10:51:30PM -0700, Dennis Allison wrote:
I've finally reached the point where the site code base is large enough that weve managed to create a version problem. <sigh> It's time to put the whole thing under source code verison control.
I don't see the best way to do this in the Zope enviroment, at least not transparently. (For example, downloading with FTP and uploading is not invarient.) What's the preferred approach?
You can try ZCVSFolder. We use it quite successfully here to synchronize 10 developement workstations. It still has a couple of quirks which are sometimes annoying, but harmless otherwise. I'd recommend the CVS version, which has a number of improvements over the last release. Marius Gedminas -- Include me out.
participants (3)
-
Dennis Allison -
Marius Gedminas -
Paul Winkler