basic integration tests
readme cleanup
implemented ssh key support for digital ocean vagrant provider
Merge pull request #17 from smdahlen/ssh-key

implemented ssh key support for digital ocean vagrant provider
bump to 0.0.3
refactored ssh key support into its own middleware using the private_key_path attribute; removed support for using the insecure vagrant key
swapped out nfs for rsync following the approach used by vagrant-aws
make sure the dev build removes old gems
remove space from debug output to align with vagrant default
remove build and test shell scripts from installed binaries
Merge branch 'ssh-key' into rebuild

Conflicts:
	lib/vagrant-digitalocean/action.rb
	lib/vagrant-digitalocean/errors.rb
	locales/en.yml
Fixed syntax error due to merge.
Merge branch 'master' into rebuild
Implemented rebuild droplet command. For the given machine, the command
rebuilds an active machine with the same IP address it had.

Additionally, a new method was added to the client to wait for an
event to complete (rather than check droplet status).
make sure to reference the test key in the debug box dir Vagrantfile
add an ssh check to the create action to avoid unready box state failure, add stuck off state check in destroy
resolve conflicts
resolve conflict
Support a user-specified SSH username.

This commit enables the user to specify a SSH username for the
provider using the ssh_username config attribute. For the initial
droplet creation and provisioning, the provider will fallback to the
root user. On subsequent execution of Vagrant commands, the
specified SSH username will be attempted instead. The user should
create the SSH username account during the provisioning process.

Additionally, better state checking for a droplet was implemented.
If a droplet is already active, calling up will have no effect. The
same is true when calling destroy, provision, or rebuild after a
droplet has been destroyed.

Closes #23 and #25.
Merge pull request #26 from smdahlen/ssh-user

Support a user-specified SSH username.