This project is a reference project for those who want to build microservice solutions with the ABP Framework.
This is a reference project for those who want to build microservice solutions with the ABP Framework.
See [the announcement](https://blog.abp.io/abp/Introducing-the-eShopOnAbp-Project) post for more info.
Live demo is on https://www.eshoponabp.com/
Live demo 👉 https://www.eshoponabp.com/
## Issues
@ -12,7 +12,7 @@ Please open issues on the main GitHub repository: https://github.com/abpframewor
## How to Run?
You can either run in Visual Studio, or using [Microsoft Tye](https://github.com/dotnet/tye). Tye is a developer tool that makes developing, testing, and deploying micro-services and distributed applications easier.
You can run it in Visual Studio or use [Microsoft Tye](https://github.com/dotnet/tye). Tye is a developer tool that makes developing, testing, and deploying micro-services and distributed applications easier.
### Requirements
@ -32,8 +32,8 @@ You can either run in Visual Studio, or using [Microsoft Tye](https://github.com
- Wait until all applications are up!
- You can check running application from tye dashboard ([localhost:8000](http://127.0.0.1:8000/))
- **Note**: If you see all of your applications keep restarting on tye dashboard or tye console, you may be facing ssl certificate issues. To diagnose the problems better, check any application logs. If it is related with SSL, developer certificate creation may have failed because of powershell issues regarding authorization. Check the powershell script running configuration and set policy for your local machine as:
- You can check the running application from `tye` dashboard ([localhost:8000](http://127.0.0.1:8000/))
- **Note**: If you see all of your applications keep restarting on `tye` dashboard or `tye` console, you may be facing SSL certificate issues. To diagnose the problems better, check any application logs. If it is related to SSL, developer certificate creation may have failed because of Powershell issues regarding authorization. Check the PowerShell script running configuration and set the policy for your local machine as follows: