ColdFusion Weekly Version 1.29 - November 20, 2006 - The "Source Control Revisited" Edition
Version 1.29 - November 20, 2006
Introduction & Comments
- What Matt has been up to
- Life, MachBlog Skins, etc.
- What Peter has been up to
- Life, Mach-II, etc.
CFReport - at 4:53
- Whither CF? More thoughts on the future of CF
- Should CF become open source?
- Configuring CF Multiple Instances with Apache Virtual Hosts
- at 10:22
- Customizable CSS on InstantSpot
- Brian Kotek wrote an article on ColdSpring for Tech Republic
- Barney Boisvert presented on ColdSpring at the Portland CFUG
- Brian Meloche's big Mach-II project is live!
- Mach-II request timeout filter
- Updated Mach-II FAQs
- RSS feeds for the Mach-II Google group
- at 19:57
- CFC-only version of Fusebox by Steve Nelson
- Dave Shuck asks, "Does your framework control you?"
- Andy Powell on Spry
- JSDocs for Spry API
- Ray Camden's Spry presentation recording
- Intel Macs will be supported in Scorpio
- Ted Patrick created a new Flex Search, powered by CF
- at 29:27
- CFUnited 2007 registration now open - $849 price through 12/31
- New web site for cf.objective() 2007 - May 3-6, 2007
- Scotch on the Rocks 2007 Announced - Thursday May 31st, and Friday June 1st
- Adobe Kuler launched - backend is CF + Model-Glue
CF_Focus - at 37:20
Source Code Management Revisited
- Lots of emails and IMs about this lately--this is great news!
- People still struggling with the specifics of the setup, some confusion on process
- Most common question is "how do I get this working on a shared development server?"
- Using source control does necessitate a change in development process, but it's a change for the better
- LOCAL development is by far the best development setup
- BUT what about my ultra-complex application that has tons of dependencies that I don't want to run locally?
- If the application can only run in one environment, such as a shared dev server, that's a fragile development process
- Couple of approaches for code integration and testing
- Simple: a project in eclipse can be set up to point to the repo on one end and a shared dev server on the other--calling an update drops all the code onto the dev server
- Better: build process pulls code from svn and deploys to target server(s)
- Benefits
- Local, isolated development--more freedom for each developer
- Freedom to refactor with impunity
- Encourages the creation of a daily build/integration process, repeatable build process in general
- Safer, better way to develop
Wrap Up - at 1:00:57
CFExit - at 1:03:00
"Mary Machine" by J.R. Byrd
(download)
