ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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 13:09:22 -07:00
parent 78f055d109
commit d6e3389cde
1 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -54,10 +54,11 @@ $ cd eShopOnContainers
With that, you'll have the code at /Users/yourUser/MyGitRepos/eShopOnContainers folder. With that, you'll have the code at /Users/yourUser/MyGitRepos/eShopOnContainers folder.
## Open the "eShopOnContainers-ServicesAndWebApps.sln" solution ## Open the "eShopOnContainers-ServicesAndWebApps.sln" solution with VS for Mac
Run Visual Studio for Mac and open the solution 'eShopOnContainers-ServicesAndWebApps.sln'. Run Visual Studio for Mac and open the solution 'eShopOnContainers-ServicesAndWebApps.sln'.
Just for testing the containers and web apps, do NOT open the other solutions, like 'eShopOnContainers.sln' as those solutions will also open the Xamarin projects and that might slow you down.
Just for running the containers/microservices and web apps, do NOT open the other solutions, like 'eShopOnContainers.sln' as those solutions will also open the Xamarin projects and that might slow you down.
After opening the solution, it is recommended to wait for a few minutes as VS will be restoring many NuGet packages and the solution won't be able to compile or run until it gets all the nuGet packages dependencies, in the first place (this time is only needed the first time you open the solution. Next times it is a lot faster). After opening the solution, it is recommended to wait for a few minutes as VS will be restoring many NuGet packages and the solution won't be able to compile or run until it gets all the nuGet packages dependencies, in the first place (this time is only needed the first time you open the solution. Next times it is a lot faster).
@ -65,6 +66,21 @@ This is VS for Mac with the "eShopOnContainers-ServicesAndWebApps.sln" solution.
![image](https://user-images.githubusercontent.com/1712635/32020102-f691b96a-b983-11e7-8960-32e2e2968d3e.png) ![image](https://user-images.githubusercontent.com/1712635/32020102-f691b96a-b983-11e7-8960-32e2e2968d3e.png)
## Run eShopOnContainers from VS for Mac (F5 or Ctrl+F5)
Make sure that the by default start-up project is the Docker project named 'docker-compose'.
Hit Ctrl+F5 or press the "play" button in VS for Mac.
IMPORTANT: The first time you run eShopOnContainers, it will take longer than the next time you launch it. Under the covers, Docker is pulling quite a few "heavy" images from Docker Hub (the public image registry), like the SQL Server image, Redis image, RabbitMQ image and the base ASP.NET Core images. That pull/download process will take a few minutes. Then, VS will launch the application custom containers plus the infrastructure containers (SQL, Redis, RabbitMQ and MongoDB), populate sample data in the databases and finally run the microservices and web apps on custom containers.
Note that you will see normal/controlled Http exceptions caused by our retries with exponential backoff, as the web apps have to wait until the microservices are ready for the first time which need first to run SQL sentences populating sample data, etc.
Once the solution is up and running, you should be able to see it in the browser at:
http://localhost:5100
# Option B: Use a CLI environment (dotnet CLI, Docker CLI with the bash shell) and VS Code as plain editor # Option B: Use a CLI environment (dotnet CLI, Docker CLI with the bash shell) and VS Code as plain editor