First off, thanks to those who replied to my questions about application integration with Farcry. Your responses were extremely helpful and set us on the right path.
So of course I want to ask the golden goose if I can please have another golden egg :-) We have a team of developers working on a particular farcry site. They're focused on integrating several apps with Farcry and adding functionality to our install to suit our particular needs. As much as we would usually appreciate sharing a dev server, we've grown accustomed to developing code on our local machines, doing peer review, checking in to CVS, and then placing it on a shared development box. We know that Farcry is meant to be a CMS first and foremost and that the content you create is expected to be deployed by being Approved ~ there is no easy way to deploy content from a staging server. We're cool with that part. What we're tripping on is the ability to develop code locally, test against the shared dev database, and somehow not get in each other's way. The site's functionality may depend on CFCs that exist only in someone's local environment. All it takes is one bad reference in the dev database (i'm thinking a container/rule combination referencing a type that is not on the shared box yet) to bring everybody to a halt. How are you handling this in your environments? Or are you able to sidestep it entirely by being the only one working on the site? TIA- Steve -- ------- Steve Rittler [EMAIL PROTECTED] --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
