4 ms·
Now, try adapting that approach to do Blue/Green deployments [1]. Imagine how that is done using configuration managers. Can you see the advantage now? [1] htt
by sergiosgc 11y ago
Now, try adapting that approach to do Blue/Green deployments [1]. Imagine how that is done using configuration managers. Can you see the advantage now?
[1] http://martinfowler.com/bliki/BlueGreenDeployment.html http://martinfowler.com/bliki/BlueGreenDeployment.html
- lisivka 11y agoI use it. Blue/Green deployments is one of main reasons to use package managers, because with package manager I can prove that two deployments are identical, including configuration files, which are also deployed using package manager. It was primary reason why we switched from configuration scripts to packages for provisioning and configuration.
- sergiosgc 11y agoExcept that you'll need to reconfigure parts of the stack post-installation. You consider that an upgrade of the configuration "package"? You're reinventing the wheel. Doable, not efficient.
- lisivka 11y agoWhy I need to reconfigure parts of the stack in first place? I am devops, so these things are automated. In general, plan your changes ahead of time, test and automate them at staging servers, prove correctness of changes, and then deploy to production. Never do anything by hands (or by configuration tools) at production servers.