Skip to content

Fix Path Issue of Pizzashack Backend in Distributed Docs #10706

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.

Sign up for GitHub

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

Merged
hisanhunais merged 1 commit into from
Feb 16, 2026
Merged

Fix Path Issue of Pizzashack Backend in Distributed Docs #10706

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...cludes/deploy/steps-to-deploy-apim-in-a-distributed-setup-with-km-separation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1101,4 +1101,4 @@ Once you have successfully configured all the API-M nodes in the deployment, you

!!! note "Optional"
The backend for the sample PizzaShack API is not included with the WSO2 API Manager distributed deployment components.
You need to set up the backend separately—either by updating the endpoint URL to point to an existing backend, or by deploying the [sample backend]({{base_path}}/assets/attachments/pizzashack.war) if you need to try out the sample PizzaShack API.
You need to set up the backend separately—either by updating the endpoint URL to point to an existing backend, or by deploying the [sample backend](/en/4.5.0/assets/attachments/pizzashack.war) if you need to try out the sample PizzaShack API.
2 changes: 1 addition & 1 deletion ...cludes/deploy/steps-to-deploy-apim-in-a-distributed-setup-with-tm-separation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -862,4 +862,4 @@ Once you have successfully configured all the API-M nodes in the deployment, you

!!! note "Optional"
The backend for the sample PizzaShack API is not included with the WSO2 API Manager distributed deployment components.
You need to set up the backend separately—either by updating the endpoint URL to point to an existing backend, or by deploying the [sample backend]({{base_path}}/assets/attachments/pizzashack.war) if you need to try out the sample PizzaShack API.
You need to set up the backend separately—either by updating the endpoint URL to point to an existing backend, or by deploying the [sample backend](/en/4.5.0/assets/attachments/pizzashack.war) if you need to try out the sample PizzaShack API.