Configuration Management For Development Environments
The following is a great batch of slides from Gareth Rushgrove. It comes from his February presentation at FOSDEM (Free and Open Source Developerss European Meeting)
I had the pleasure of speaking at Fosdem last weekend to a packed Configuration amd systems management devroom.
My presentation covered some of the same ground as recent blog posts, namely why you should be using virtualisation and config management tools to manage your local development environment.
People even said nice things about it:
@garethr basically has this subject completely covered. He’s even advocating the correct editor. excellent #fosdem talk
All in all another good event, I have notes about some of the other talks I went along to that I’ll try write up soon.
Source: http://morethanseven.net/2011/02/08/Configuration-management-for-development-environments.html
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
Comments
Robert Craft replied on Thu, 2012/01/26 - 6:12am
Software configuration management (SCM) is the task of tracking and controlling changes in the software.
SCM concerns itself with answering the question "Somebody did something, how can one reproduce it?" Often the problem involves not reproducing "it" identically, but with controlled, incremental changes. Answering the question thus becomes a matter of comparing different results and of analysing their differences. Traditional configuration management typically focused on controlled creation of relatively simple products. Now, implementers of SCM face the challenge of dealing with relatively minor increments under their own control, in the context of the complex system being developed. According to another simple definition: Software Configuration Management is how you control the evolution of a software project.
Spring Security