Updated 04. Setting eShopOnContainer solution up in a Mac, VS for Mac or with CLI environment (dotnet CLI, Docker CLI and VS Code) (markdown)

Cesar De la Torre 2017-10-25 15:43:26 -07:00
parent ddea9dde0c
commit 91919843ad

@ -230,24 +230,22 @@ You could generate the binaries manually, with 'dotnet publish', but for your co
In addition, it runs the client build commands using *npm* to build the SPA application
assets. Finally, it will remove old docker containers and images.
After you've finished the build, you can create the necessary containers using
`docker-compose`:
After you've finished the build, you can create the Docker images defined at the docker-compose.yml file by using `docker-compose build`:
```bash
$ docker-compose build
```
The above command creates the images for the eShopOnContainers application. To run, you
use `docker-compose` again:
To run the containers, you use `docker-compose up` again:
```bash
$ docker-compose up
```
You could also go ahead and directly run `docker-compose up` and it will first build the Docker images like when you run `docker-compose build`, though.
The first time you run this command, it will pull the necessary docker images
from Docker hub. That will take some time. Once the images have been pulled,
the application will start and you can test it out using the browser and the
addresses shown [above](#running-the-application).
The first time you run `docker-compose up`, it will pull the necessary docker images from Docker hub. That will take some time. Once the base Docker images have been pulled, the application will start and you can test it out using the browser and the addresses shown [above](#running-the-application).
For testing the MVC web app, run `http://localhost:5100` in any browser, so you'll see it like the following:
# Configuring the app for Authentication and access from remote client apps