Vagrant: why and how

Our experience with Vagrant for WordPress development in Motork

Transcript

1. Vagrant: why and how. Giustino Borzacchiello - MotorK HQ - 15/07/2016
2. Why?
3. The old days: PHP and MySQL
4. Nowadays: PHP MySQL Java Grails Solr JavaScript Backbone.js React npm Grunt gulp.js Sass Less.js postcss CouchDB memcached phpMyAdmin Git webgrind Node. js nginx Apache WordPress
5. Installation
6. Configuration
7. Works on my machine
8. Multiple projects
9. Different operating systems
10. Vagrant is a tool for building, automatically, complete development environments, sandboxed in a virtual machine.
11. How?
12. Install Vagrant
13. Install VirtualBox
14. $ vagrant init hashicorp/precise64
15. $ vagrant up
17. $ vagrant status
18. $ vagrant ssh
19. $ vagrant suspend
20. $ vagrant halt
21. Demo
22. Use case: WordPress development environment in MotorK
24. Standing on the shoulders of giants: VVV
25. Our challenges: Our solutions
26. Private repositories: SSH forwarding
27. Database sync with production: Single repo with dumps
28. Windows: Linux/Mac
29. What’s missing?
30. Providers
31. Provisioners
32. Multiple machines
33. Machine sharing
34. Takeaways
35. If my hard disk dies tomorrow, how much time should I spend to be productive again?
36. Automate all the things!
37. Thank you!