Update README with a better installation process for Vagrant users

Author: Julien Neuhart

README.md

@@ -62,17 +62,7 @@ On Linux and macOS, run `sudo nano /etc/hosts` to edit it.
 
 On Windows, edit the file `C:\Windows\System32\drivers\etc\hosts` with administrative privileges.
 
-### Vagrant
-
-Check there is no application running on port 80 (like Apache or another virtual machine).
-
-If OK, run `make vagrant`, then `vagrant up`, and finally `vagrant ssh` to connect to the virtual machine. 
-From here, you'll be able to run all the next commands like Linux users!
-
-> Update the variable `VAGRANT_PROJECT_NAME` from the [Makefile](Makefile) with your project name.
-> Only use alphanumeric characters (no spaces, distinguish words with `_` or `-`).
-
-### Starting the Docker Compose stack
+### First start
 
 Copy the file [.env.dist](.env.dist) to a file named `.env`. For instance:
 
@@ -83,12 +73,44 @@ cp .env.dist .env
 > Edit the [.env.dist](.env.dist) by updating the default values of `DOMAIN`, `MYSQL_DATABASE` and `APP_SECRET`
 > environment variables.
 
-Next, make sure there is no application running on port 80 (Vagrant users can skip this check).
+---
+
+#### Vagrant user
+
+"Comment" the `STARTUP_COMMAND_3` and `STARTUP_COMMAND_4` environment variables from the `api` service 
+in the [docker-compose.yml](docker-compose.yml) file.
+
+Next, run:
+
+```
+docker-compose up webapp api
+```
+
+📣  This command start the `webapp` and `api` service. While booting, these services install the JavaScript
+and PHP dependencies. We cannot do that directly in the Vagrant VM as `yarn` and `composer install` fail miserably the
+first time.
 
-**📣  Vagrant users: the first time you start the Docker Compose stack, you have to "comment" the following 
-environment variables from the `api` service in the [docker-compose.yml](docker-compose.yml) file: 
-`STARTUP_COMMANDS_2`, `STARTUP_COMMAND_3`, and `STARTUP_COMMAND_4`. Indeed, `composer install` fails miserably, 
-but there is a workaround. See below.**
+Once the services have installed the dependencies, you may stop them with:
+
+```
+CTRL+C
+docker-compose down
+```
+
+Don't forget to uncomment the previous environments variables from the `api` service 
+in the [docker-compose.yml](docker-compose.yml) file.
+
+Next, check there is no application running on port 80 (like Apache or another virtual machine).
+
+If OK, run `make vagrant`, then `vagrant up`, and finally `vagrant ssh` to connect to the virtual machine. 
+From here, you'll be able to run all the next commands like Linux users!
+
+> Update the variable `VAGRANT_PROJECT_NAME` from the [Makefile](Makefile) with your project name.
+> Only use alphanumeric characters (no spaces, distinguish words with `_` or `-`).
+
+---
+
+Next, make sure there is no application running on port 80 (Vagrant users can skip this check).
 
 Good? You may now start all the Docker containers with the following commands:
 
@@ -99,15 +121,11 @@ make up
 It may take some time as each container will also set up itself, such as installing dependencies (PHP, JavaScript, etc.), 
 compiling sources (JavaScript), or running migrations to set up the database structure.
 
-**📣  In some cases, the `api` service will try to run the migrations before the `mysql` service is ready. If so, restart
-the `api` service with `docker-compose up -d api`.**
+**📣  In some cases, the `api` service will try to run the migrations before the `mysql` service is ready. 
+If so, restart the `api` service with `docker-compose up -d api`.**
 
 The containers will be ready faster next time you run this command as the first run is doing most of the setup.
 
-**📣  Vagrant users: enter the `api` service with `make api`. Here, run `composer install --prefer-source` 
-(and prepare some coffee). When done, exit the container, uncomment the previous environments variables,
-and rerun `make up`.**
-
 Once everything is ready, the following endpoints should be available:
 
 * http://traefik.companies-and-products.localhost (Reverse proxy, the entry point of all the HTTP requests)