1 / 3
Beautifully stable
Russ wired the shop to go live the moment anyone saved a file. June pressed save once and nine thousand customers read a front page saying 'Autumn Sa'.
The mistake
Russ connects the production deploy directly to a file-save watcher, so every save from any editor goes straight to the live shop. There is no commit, review, build or test step in between, so each half-finished edit is published to customers. He then switches it off by editing the config through that same save-to-deploy path, so the half-edited config gets deployed and takes the shop down. Continuous deployment means shipping each finished, checked change, not every save of a file someone is still working on.
- deploys
- process
- frontend
- ecommerce
- release