Browse Source

updated get-started microservice document

pull/23278/head
Yunus Emre Kalkan 10 months ago
parent
commit
55e5c81dc8
  1. BIN
      docs/en/get-started/images/abp-studio-microservice-solution-runner-applications.png
  2. BIN
      docs/en/get-started/images/abp-studio-microservice-solution-runner.png
  3. 2
      docs/en/get-started/microservice.md

BIN
docs/en/get-started/images/abp-studio-microservice-solution-runner-applications.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 39 KiB

After

Width:  |  Height:  |  Size: 53 KiB

BIN
docs/en/get-started/images/abp-studio-microservice-solution-runner.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 123 KiB

After

Width:  |  Height:  |  Size: 132 KiB

2
docs/en/get-started/microservice.md

@ -154,7 +154,7 @@ In the *Solution Runner* section (on the left side) you can see all the runnable
> A leaf item in the *Solution Runner* is called as an *Application* as it is an executable application.
As shown in the figure above, the executable applications are grouped into folders like `apps`, `gateways`, `infrastructure`, and `services`. You can start/stop them all, a group (folder) of them, or one by one.
As shown in the figure above, the executable applications are grouped into folders like `apps`, `gateways`, and `services`. You can start/stop them all, a group (folder) of them, or one by one. The `Containers` branch contains the needed docker containers for the applications.
Before running the applications, you can run the all application by right-clicking the root item in the *Solution Runner* and select *Build* -> *Build All* action. However, you don't need to do that, because ABP Studio builds the applications before running them by default.

Loading…
Cancel
Save