Just to add some thoughts to this. It really doesn't take much to have a working development setup that can be thrown into a zip and then scripted out for installation. Especially if you're using Apache/MySQL. I've got a zip that I hand out to folks that I collaborate with that contains Railo/MySQL/Eclipse/Apache. They just have to run 3 batch files to install the services for Apache/MySQL/Resin and they have an identical setup to what I use. The other nice bit is every time I add a new site, they just need to download a new zip to add it into the mix.
This can be done with ACF as well, as you don't really need an install there, just getting the services in place works fine. Even if you want to run the install, it's not all the time consuming. Heck, isn't there an "unofficial" means of running a silent install for it? And from a maintenance standpoint, you could set up shares on each dev machine that are a one to many point (windows allows for this). You could patch a central machine and have that propagate out to each of the "many" machines. It would require a service restart, but it's doable. In short, I personally feel that running development locally is where it's at. You might have to invest some time up front, but you should save effort when it comes to ongoing maintenance of the systems. And when coupled with source control, it should help a larger team from stepping on each others work. -- Matthew Williams Geodesic GraFX www.geodesicgrafx.com/blog twitter.com/ophbalance ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:354255 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
