To build on this idea, look at Vagrant. It allows your IT department (or whoever's responsible) to maintain a script that loads a VM, necessary assets, and code. I've written a Vagrant script for Railo:
https://github.com/bdcravens/railo-vagrant Here's a Chef recipe Nathan Mische wrote for CF10 (which can be used in a Vagrant setup): https://github.com/nmische/chef-coldfusion10 Vagrant is awesome. Run a script, get a VM. Dev against a local directory on your machine, and check into source code repo as necessary. When you're done, shut the machine off. The shared directories don't go away (so you keep working code), but everything else does, until you need to spin it up again. Currently works against VirtualBox, VMWare coming soon. Billy Cravens [email protected] On Jan 30, 2013, at 6:52 PM, Andy Ousterhout <[email protected]> wrote: > > Why not just have a local VMware image for developer unit testing? > > Sent from my iPhone > > On Jan 31, 2013, at 7:51 AM, Michael Christensen <[email protected]> wrote: > >> >> First of, let me thank all of you for your (quite lively) inputs. >> >> The discussion did spiral a bit out of control in a GIT vs SVN tussle, but I >> understand and can respect that people have strong opinions as to which >> systems they prefer. >> >> I also wholeheartedly agree, that there are certain advantages to be gained >> by each developer having a working copy of the code on their local machines. >> I would, however, contest the absoluteness of this as the only way to go. >> >> While it is true, that the CF Developer licensing does allow for each >> developer to run a CF server locally without paying a license fee, the time >> spent by the IT department setting up and supporting 50+ websites (plus our >> backend/admin software) on each developer machine does come at a cost. >> Add in the cost of additional licenses for 3rd party components (like >> ImageGlue or ISAPI rewrite for example) and the cost of being able to run >> code locally can add up quite quickly. >> >> For us at least, running on a shared codebase with 1 development server and >> all code available via a webpath (usually mounted as a drive for >> convenience) works quite well and has done so without major snafus for 10+ >> years. >> >> Is this an "oldschool approach"? Very much so. >> Is it a good solution? Maybe not for every company, but it works for us. >> >> I understand, that our setup makes running version/source control very >> difficult and it is a conclusion that I feared I might reach, when I posted >> the question initially. >> >> I think that I may have to go back and have a long, hard think about how we >> will proceed from here. >> >> If any of you, who are running a setup where each developer runs the code >> locally, I would be very appreciative if you could give me 30 minutes to an >> hour of your time, so I might pick your brain as to how you have gone about >> getting this setup and how you maintain it (I think this is probably best >> done over Skype). >> >> So once again, thank you guys so much for all your input :) >> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:354199 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
