The basic requirement is to have a local web server on your machine that you can run WordPress on. There are a number of different ways to do that; MAMP<\/a>, WAMP<\/a>, XAMPP<\/a>, etc. The problem with those solutions is that they can be difficult to set up, especially if you want to run more than one copy of WordPress. Another way to run a local web server is to install a virtual machine that runs independently of your desktop or Laptop OS. Again, there are a number of solutions, both free and paid. The solution we recommend is VirtualBox and Vagrant. This combination allows you to create virtual environment much closer to a real web server, and have it automatically set up everything, including WordPress, correctly for you. The full solution we recommend is one called Varying Vagrant Vagrants<\/a> (VVV), originally developed by 10up<\/a>\u00a0and transitioned to a community organisation in 2014.<\/p>\n The following instructions, taken from the VVV Github page<\/a>, apply to Windows, Mac, and Linux environments.<\/p>\n Vagrant<\/a>\u00a0is a “tool for building and distributing development environments”. It works with\u00a0virtualization<\/a>\u00a0software such as\u00a0VirtualBox<\/a>\u00a0to provide a virtual machine that is sandboxed away from your local environment.<\/p>\n Fancy, yeah?<\/p>\n","protected":false},"excerpt":{"rendered":" Getting Started The basic requirement is to have a local web server on your machine that you can run WordPress on. There are a number of different ways to do that; MAMP, WAMP, XAMPP, etc. The problem with those solutions is that they can be difficult to set up, especially if you want to run … Continue reading Setting Up Your Machine for Contributor Day<\/span> <\/a>What is Vagrant?<\/h3>\n
<\/a>The First Vagrant Up<\/h3>\n
\n
\n
\n
vagrant<\/code>\u00a0will now be available as a command in your terminal, try it out.<\/li>\nvagrant -v<\/code>\u00a0to check the version. You may want to consider upgrading if a much older version is in use.<\/li>\nvagrant plugin install vagrant-hostsupdater<\/code>\n\n
hosts<\/code>\u00a0file to access the provisioned VVV domains in your browser.<\/li>\nhosts<\/code>\u00a0file that looks like this:\u00a0192.168.50.4 vvv.dev local.wordpress.dev local.wordpress-trunk.dev src.wordpress-develop.dev build.wordpress-develop.dev<\/code><\/li>\nvagrant plugin install vagrant-triggers<\/code>\n\n
vagrant halt<\/code>\u00a0and\u00a0vagrant destroy<\/code>.<\/li>\ndb_backup<\/code>\u00a0script will run on halt, suspend, and destroy that backs up each database to a\u00a0dbname.sql<\/code>\u00a0file in the\u00a0{vvv}\/database\/backups\/<\/code>\u00a0directory. These will then be imported automatically if starting from scratch. Custom scripts can be added to override this default behavior.<\/li>\n<\/ul>\n<\/li>\n\n
git clone git:\/\/github.com\/Varying-Vagrant-Vagrants\/VVV.git vagrant-local<\/code><\/li>\ncd vagrant-local<\/code><\/li>\nvagrant up<\/code>\n\n
su<\/code>\u00a0password may be required<\/em><\/strong>\u00a0to properly modify the hosts file on your local machine.<\/li>\n<\/ul>\n<\/li>\n\n