#Working Locally with Wordpress#
![picture of Ryan Tvenge](img/me.jpg)
###[@rtvenge](https://twitter.com/rtvenge) | [ryantvenge.com](http://ryantvenge.com/)###
#Working off Server
* See results right away
* Don't have to drag files up to the server
#Ever seen this?
![php error page](img/blankpage.png)
#Pitfalls of an FTP Commando#
* Breaking live site is really easy
* Don't have backups of files
* Possibly can't work in your own text editor
* Can't work offline
* Can't use version control (Git)
#Software We'll be using:#
* Get's lamp stack working in OSX.
* If using Windows, you can use [WAMP](http://www.wampserver.com/en/)
* [Desktop Server](http://serverpress.com/products/desktopserver/) is a good alternative (OSX, Windows).
* [WP Migrate DB](http://wordpress.org/plugins/wp-migrate-db/) (Wordpress Plugin)
* Helps bundle up database to migrate.
* Pro version pushes and pulls databases from Wordpress Admin.
* [BackupBuddy](http://ithemes.com/purchase/backupbuddy/) is another good option.
#What we're going to do:#
* Get LAMP stack up and running.
* Create MySQL database via phpMyAdmin
* Install Wordpress locally
* Migrate database up to server using WP Migrate DB
#How to make this process even better#
* Start checking local code into version control system ([Git](http://git-scm.com)).
* Have Git repo auto-publish new files to production site. ([Beanstalk](http://beanstalkapp.com)).
* Whole 'nother ball of wax. Next talk? :)
* [Vagrant](http://www.vagrantup.com) uses virtual machines to completely emulate your production server. ([Jeremy Felt's Talk](http://wordpress.tv/2013/12/31/jeremy-felt-hi-wordpress-meet-vagrant-2/))
* Twitter: [@rtvenge](https://twitter.com/rtvenge)
* website: [ryantvenge.com](http://ryantvenge.com/)
* GitHub: [rtvenge](http://github.com/rtvenge/)