Update WP stable as WP trunk is updated
VVV confirmed to work with Vagrant 1.2.4
Merge remote-tracking branch 'xteam/stable-wp-core-update'
Listen for HTTPS requests and generate SSL cert
Update contributors list
Add 'listen 443 ssl' to local-nginx-example.conf-sample
Merge remote-tracking branch 'xteam/https-sites'
Make server private key generation quieter

With the way that Vagrant works when scrolling screens through, the private key generation ends up being a looooooong series of red dots. By storing the command as we issue it, we can provide a nice one or two line output as we go instead.

We'll apply this to other commands as well, this just happens to be the current longest offender.
Clean up some spacing for readability
Make the SSL cert signing a bit quieter as well

See changes from d7d1595 for explanation
Spacing and wording changes in provisioning output
Change Vagrant box name to precise32 from std-precise32

precise32 is used in Vagrant doc examples and is common throughout the Vagrant community for configurations built using the Ubuntu 12.04 box provided via Vagrantup.com.

This will cause an additional 280MB box to be downloaded for anyone who has used VVV before. The previous box can be removed with `vagrant box remove std-precise32`

Closes #104
Change VM host name to vvv from precise32-dev

Per #105, vvv is more descriptive for the scope of our VM. This is a possible breaking change if any custom work was done on top of VVV as a scaffold, so we'll note that in the changelog as well.
Update changelog for 0.9-working
Add mu-plugin to fix Nginx permalink issue

Because WordPress cannot correctly identify whether rewrite
capabilities are enabled on this server setup, "index.php" is getting
injected into the top level of the permalink structure (e.g.
http://www.mysite.com/index.php/sample-post/). Hooking into WP's
`got_rewrite` filter to explicitly specify that rewrites are available
removes the issue, as explained in the closing comments for the
core Trac ticket 13201 and demonstrated in the code for rtCamp's
"Nginx Helper" plugin.

In the interest of clarify, this plugin uses the simplest possible
code (i.e., no plugin Class boilerplate).

References:

Trac ticket for Nginx permalink issues
http://core.trac.wordpress.org/ticket/13021#comment:4

Nginx Helper plugin
http://wordpress.org/plugins/nginx-helper/

Fixes #85
Dynamically report the virtual machine's IP address during provisioning

* Uses a bash command to store the VM IP into a variable for use throughout provisioning. Thanks @petemall!
* Removes the IP restriction in the default.conf Nginx configuration

Closes #94
Update contributors list
Remove last pieces of the flags system

The flags system was a well intentioned way to disable certain parts of the provisioning script from running. It quickly whittled back down to one flag, which controlled the WordPress unit tests. Rather than continuing to maintain this weird little `flags` directory, this commit removes that in favor of creating an empty `www/wordpress-unit-tests` directory to stop unit tests from being checked out or updated.

Closes #91
Change network check to ping 8.8.4.4 rather than 8.8.8.8

8.8.8.8 was not responding today, so using Google's primary DNS server instead.

See #107, a better solution is probably needed.
Remove flags from .gitignore

Related to #91