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?
Everything we do at Daemon (or just about) is from the workstation. We only deploy to a shraed server for QA or show and tell. If someone is working on a new set of content types or rules etc that is going to populate the db with data that is going to break things we'd likely either write code to supress the error (this is typical behaviour in the presentation layer) or just copy the database for that person and have them work on their own database till their work was ready to integrate.
-- geoff http://www.daemon.com.au/
--- 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/
