Local Development Environments

This was a short talk I gave at a local WordPress meetup, where I discussed all of the ways I've developed code, from doing it live to using Vagrant and Capistrano.

Transcript

1. Local Development Environments by: Joe Casabona joe@casabona.org @jcasabona
2. Who Am I? 2
4. Why this Topic? 4
5. 5 Developing on a live server Editing theme files through WP admin Not properly testing. All Bad!
6. Possible Solutions! 6
7. 7 Prod should ONLY have working code! Dev should be for everything else! Good hosting providers should have this for you Dev & Prod Servers!
8. 8 Easy Solution! Download and you have a local server PHP, MySQL, Apache XAMPP even has a WordPress installer There are pitfalls… MAMP | XAMPP
9. 9 Great place to keep code Versioning Automatic Backups Fantastic for trying things out Fantastic for Teams Good hosts will let you deploy code from git! Git | Github
10. Heavy Hitters 10
11. 11 Emulates Servers & Operating Systems Basis for a lot more advanced tools like… Virtual Box
12. 12 “Create and configure lightweight, reproducible, and portable development environments.” Vagrant Set up a config file Spin up a temp server Tear it down when you’re done or need to start 
 over Resource: Varying Vagrant Vagrants
13. 13 VVV “The primary goal of Varying Vagrant Vagrants (VVV) is to provide an approachable development environment that matches a typical production environment.” Resource: Varying Vagrant Vagrants
14. 14 “A remote server automation and deployment tool written in Ruby" Capistrano Spin up local servers Deploy from your machine to a server Integrates with git Complete Magic.
15. 15 Questions?