Update project's README with new docker-compose instructions; modify …

…./console to use docker-compose directly

README.md

@@ -29,10 +29,7 @@ Project is given with a [PHPDocker.io](http://phpdocker.io) generated environmen
   * `composer install`
   * `bower install`
   * `php bin/console assets:install --symlink --relative`
-  * cd into the `phpdocker` folder and either `docker-compose up -d` or `vagrant up`. More specific information on [phpdocker/README.md](phpdocker/README.md).
+  * cd into the project folder and run`docker-compose up -d`. More specific information on [phpdocker/README.md](phpdocker/README.md).
   * You can then head off to the `/generator` route; you'll need to run `bin/console doctrine:schema:create` within the PHP container (or use the `console` script at the root of the project) to avoid SQL errors on the homepage
 
-**Note:** you'll notice a `console` script at the root of the project. It does some voodoo to run `bin/console` within the container. There are several limitations however:
-  * Needs fixing to properly work through vagrant as the `.vagrant` folder is not at the root of the project
-  * It is not fully interactive. Any symfony commands that require user prompt after running the command (for instance, doctrine migrations) will not work
-  * We really should bundle it on the generated environments for other people to use
+**Note:** you'll notice a `console` script at the root of the project. It does some voodoo to run `bin/console` within the container.

console

@@ -1,2 +1,2 @@
 #!/usr/bin/env bash
-bin/run-in-container php bin/console $@
+docker-compose exec --user www-data php-fpm bin/console $@