& Ops • Automation • Monitoring • Cost increase • The market 5 5 Where Do We Need To Go? ⇢ Comfortable with both tools & service platforms ⇢ Runs on my machine (and in the cloud) ⇢ Continuous improvement, project maintenance ⇢ Full transparency & focus on QA (write tests, performance, security) ⇢ Short-lived branches, short time-to-market (features) ⇢ Easily switch between service platforms
(README) • Manual configuration steps • Special scripts for setting up project • config-local-dist.php & similar • Disable linting, no tests • A myriad of configuration files (and tools) • Long-lived branches & git-flow • Start monitoring late • Start deploying late Application & Target Environments Favor • Standard procedures for getting started (short paragraph in README) • Everything under version control (what is needed to get started) • Treat your dev machine as a (standard) target environment • Use getenv(‘VALUE’, ‘default’) etc. • Short-lived feature branches • Deploy & monitor from “commit 1” 14 14
development and deployment 16 16 How we ensure independence Deployment-side • No application-specific details • Standard approaches (CD) • Keep platform-specific differences to a minimum
immer gute Frauen und Männer, die wir anhand ihrer individuellen Stärken, Erfahrungen und Wünsche in die bestehenden Teams integrieren. Bewirb dich noch heute! Follow us on Twitter! @vshn_ch VSHN AG - Neugasse 10 - CH-8005 Zürich - +41 44 545 53 00 - https://vshn.ch/ - [email protected] 18