-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Documentation: Enhanced Studio documentation #24558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
monitoring applicationsThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request enhances the ABP Studio documentation by adding more detailed explanations, clarifying existing content, and fixing inconsistencies across multiple documentation files. The changes improve user understanding of Studio features including Suite integration, Solution Explorer capabilities, application running/monitoring, and Kubernetes integration.
Changes:
- Enhanced Suite documentation with clearer explanations of context menu options and automatic version matching
- Expanded Solution Explorer documentation with detailed descriptions of Analyze features, Open With options, and README support
- Improved Running Applications documentation with comprehensive property descriptions and Open With submenu details
- Significantly enhanced Monitoring Applications documentation with detailed tables, subsections, and feature explanations
- Fixed typo in Kubernetes documentation ("Refrest" → "Refresh")
- Added new Metadata and Secrets concepts with hierarchical structure explanations
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/en/studio/working-with-suite.md | Enhanced context menu documentation and added automatic version matching section |
| docs/en/studio/solution-explorer.md | Added Analyze feature documentation, Open With options, and README support across solution/module/package levels |
| docs/en/studio/running-applications.md | Expanded Properties section with detailed explanations and added Open With submenu documentation |
| docs/en/studio/monitoring-applications.md | Comprehensive restructuring with detailed tables, subsections, and feature descriptions for monitoring features |
| docs/en/studio/kubernetes.md | Fixed typo in context menu option and added Kubernetes service context menu documentation |
| docs/en/studio/concepts.md | Added comprehensive Metadata and Secrets documentation with hierarchy and common keys |
| @@ -215,13 +222,28 @@ We can open the *Application Properties* window to change *Launch url*, *Health | |||
|
|
|||
|  | |||
Copilot
AI
Jan 12, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a typo in the filename reference. It should be "solution-runner-properties" not "solutioın-runner-properties" (note the special character ı instead of i).
|  | |
|  |
| - **Health check endpoint**: Endpoint for controlling the health status of the application periodically. If the application doesn't have a endpoint for health check, you can enter `/` to use the home page of the application as health check endpoint. | ||
| - **Launch URL**: The URL used when browsing the application. This is the address where the application is accessible. | ||
| - **Kubernetes service**: A regex pattern to match Kubernetes service names. When connected to a Kubernetes cluster, ABP Studio uses this pattern to find the corresponding Kubernetes service and uses its URL instead of the Launch URL. This applies to *Browse*, *Copy URL*, and *Health UI* features. For example, if your Helm chart creates a service named `bookstore-identity-service`, you can use `.*-identity-service` or `bookstore-identity.*` as the pattern. For [microservice](../get-started/microservice.md) templates, this is pre-configured. | ||
| - **Health check endpoint**: Endpoint for controlling the health status of the application periodically. If the application doesn't have an endpoint for health check, you can enter `/` to use the home page of the application as health check endpoint. |
Copilot
AI
Jan 12, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grammar error: "an endpoint" should be used instead of "a endpoint" because "endpoint" starts with a vowel sound.
Co-authored-by: Copilot <[email protected]>
No description provided.