Dusty

* **New**
* Host names specified in app specs (`host_forwarding.host_name`) can now be used from inside any Dusty app container - previously they only worked from the host Mac.
* **Misc**
* The Dusty VM now reserves 10.174.249.x for NAT routing inside the VM. Previously, it reserved 10.0.2.x.

* **Misc**
* Dusty now adds any known hosts specified in the `repo` field of specs to root's known host file. Previously, users had to manually add hosts as root, or Dusty couldn't pull repos other than GitHub.
* `dusty upgrade` will check that requirements of the new version are satisfied before completing the upgrade.
* Assets are now persisted between restarts of the Dusty VM.

* **Breaking**
* Dusty has upgraded to [Docker Machine](https://docs.docker.com/machine/)! This replaces boot2docker as the tool for managing Docker-enabled VMs. Migration help can be found [here](https://gist.github.com/jsingle/bd1d8c04f45040b24c28)
* The setup override flag `--boot2docker_vm_memory` has been renamed to `--vm_memory`
* **New**
* Managed repos are now updated in parallel during `dusty up` and `dusty test`.
* New command `dusty env` can set environment variable overrides per app or service. These variables can also be read from a file, as with Docker Compose's `env_file` key.
* New command `dusty assets` can be used to place files like private keys inside containers, without the need to keep them in version control.
* **Misc**
* Dusty now uses the name `dustyInternalNginx` for its own nginx container to make naming conflicts less likely.

* **Breaking**
* Dusty now uses NFS instead of rsync to get repository code from your host Mac to running containers.
* The `sync` commands no longer exist, due to the move to NFS.
* The `restart` command no longer takes a `--no-sync` flag, due to the move to NFS.
* **New**
* Dusty now attempts to fix a known problem with boot2docker networking, resulting in up to a 10x improvement in network performance. See [this boot2docker issue](https://github.com/boot2docker/boot2docker/issues/1022) for more information.
* Bundles can now specify services, just as they specify apps.
* **Misc**
* `test.once` commands that fail now cause the entire test run to fail immediately.
* When running all test suites, a tabular summary of test results is now printed at the end of the run
* Repos specified with `https:` or `file:` now are successfully mounted to containers by Docker Compose
* Fixed various issues with using fully specified `ssh://userhost:port/path` URLs for repos

* **Breaking**
* Dusty now removes data volumes when removing containers. Containers needing to persist data should use volume mounts inside of `/persist` in the boot2docker VM.
* **New**
* Dusty no longer requires nginx to be installed on your Mac! Dusty now runs a containerized nginx inside Docker instead. All other functionality around host forwarding is unchanged.
* Dusty's socket location can now be customized via the `DUSTY_SOCKET_PATH` environment variable
* Dusty will use HTTPS to clone public repos which explicitly specify in their URL to use HTTPS
* `dusty logs` now supports a `-t` option to show timestamps on the logging output
* **Misc**
* `dusty upgrade` will now successfully upgrade Dusty from a RC version in all cases
* Images with an `ENTRYPOINT` defined now work correctly when used as the basis for a Dusty app
* All apps are now run as root in-container, via `user: root` in Docker Compose
* `dusty status` now shows the status of Dusty's nginx container and has received some performance improvements

* **Breaking**
* All rsync commands which write data to the VM (sync and disk restore) now remove any files present in the destination directory but not in the source directory. This should make it easier to reason about what is on disk on the VM side of sync. However, files written into source directories at runtime will now be deleted by sync operations.
* **New**
* `dusty upgrade` can now be used to upgrade to a release candidate