Updated 03. Setting the eShopOnContainers solution up in a Windows CLI environment (dotnet CLI, Docker CLI and VS Code) (markdown)

Cesar De la Torre 2018-01-02 15:41:55 -08:00
parent c36ace6e72
commit 9953dabbe1

@ -4,12 +4,14 @@
## Want to try it out from the CLI? ## Want to try it out from the CLI?
Main steps: Main steps to run on the CLI command window:
   
``` ```
- Git clone https://github.com/dotnet/eShopOnContainers.git - Git clone https://github.com/dotnet/eShopOnContainers.git
- Docker-compose -f docker-compose.ci.build.yml up - cd eShopOnContainers
- Docker-compose build
- Docker-compose up - Docker-compose up
(Alternatively, you can directly just run Docker-compose up and it will run the "build" command, first)
``` ```
NOTE: In order for the authentication based on the STS (Security Token Service) to properly work and have access from remote client apps like the Xamarin mobile app, you also need to open the ports in your firewall as specified in the procedure below. NOTE: In order for the authentication based on the STS (Security Token Service) to properly work and have access from remote client apps like the Xamarin mobile app, you also need to open the ports in your firewall as specified in the procedure below.
For further instructions, especially if this is the first time you are going to try .NET Core on Docker, see the detailed instructions below. This is also important in order to make the SPA app (Single Page Application) to work as there are some considerations (npm install, etc.) in regards when using NPM from Windows and Linux (the build container). For further instructions, especially if this is the first time you are going to try .NET Core on Docker, see the detailed instructions below. This is also important in order to make the SPA app (Single Page Application) to work as there are some considerations (npm install, etc.) in regards when using NPM from Windows and Linux (the build container).