This document discusses improving workflow through automation from development to production. It recommends automating tasks like saving source code, continuous integration builds on code pushes, and deployments. Continuous integration builds should run tests, process assets, and publish results on every code change. Deployments should be automated and monitored to simplify the process from development to production. Automating workflow from start to finish helps speed up development and ensure quality.

1. Improve your workflow
development, continuous integration, deployment
Adam Štipák | @new_POPE | adam@rekurzia.sk

2. Who I am?
● full stack developer (since 2006)
● Sven Creative
● Sygic
● Diagnose.me
● and other “secret” projects

3. What is the problem?
Manual work
is so slooow!

4. Solution?!
automate!
automate!!
automate!!!

5. Nice! But when? Where? How?
● as soon as possible
● as much as possible
● from save source code up to production

6. 1. development

7. Install a project
2 (3) commands (git clone, install, run)
or use

8. Save the source code
Editors have an autosave.
PHPStorm

9. Task runners
play for YOU!

10. “auto refresh”
“Time-saving synchronised browser testing.”
http://www.browsersync.io/

11. Conclusion
1. save the code
2. do work
3. autorefresh
4. profit!

12. 2. continuous integration

13. Team player
repeat, repeat, repeat ...

14. Builds
“deployable package”

15. Build process
1. on every push to repository (every branch)
2. static code analysis
3. install dependencies (libs, packages)
4. setup DB (migrations)
5. process assets (JS, CSS, images)
6. run tests
7. publish results

16. Process assets

17. Run tests

18. Publish build result

19. 3. deployments

20. Simple, simple, simple
best deployment = automatic deployment
Friday is a weekday, not “no deployment” day

21. Deployment is not the end...
Monitor it...

22. Monitoring

23. Conclusion
Tools are here.
So use it.

24. Thanks
Adam Štipák | @new_POPE | adam@rekurzia.sk