> The bare bones way takes a good amount of initial work, but mostly it's a learning experience. If my prod environment disappears over night I want to be able

> The bare bones way takes a good amount of initial work, but mostly it's a learning experience. If my prod environment disappears over night I want to be able to restore everything as fast as possible. Otherwise my boss will be very unhappy and I will be promoted to customer :D. > I feel a project is right when I can just git clone it (a few megabytes of data at most) I don't know your experience but especially small projects often have some difficulties installing all dependencies correctly. The fun starts when you don't run a widely supported distro like Ubuntu. If I want to run an old version of the production software I pull the image version X and execute it. I know that everything in the package has the right version and works like it used to. Tests have been executed and the version in the image has proven to meet the standards back then. > But, I doubt these technologies are a replacement for an ergonomic build environment If you build software for larger customer bases you will most likely encounter some kind of clustering. Most large companies have already adapted this way. For personal and small projects it certainly is overkill. > get some quick feedback on a code change ...wait, do you deploy to prod without tests and no direct way to role back the changes?