Skip to content

fix broken links in ADR EnSight Docs #204

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
merged 1 commit into from
Jul 8, 2025
Merged

fix broken links in ADR EnSight Docs #204

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 2025R2/adr-25-r2/http-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ If the GET pathname starts with /ansys/, then the directory content served up wi

## EnSight REST API Service

Starting with 2024 R1, EnSight now supports a [REST API](https://ensight.docs.pyansys.com/dev/rest_api/rest_api.html).
Starting with 2024 R1, EnSight now supports a [REST API](https://ensight.docs.pyansys.com/version/stable/rest_api/rest_api.html).
Websocketserver can be configured to serve up this API as well. To do this, websocketserver needs to be able to create a gRPC connection to the EnSight instance. The --grpc_port command line option is used for this. It is assumed the host is the same as --client_hostname. Note that one must provide a security key in this case. That key will be used as the sessionid for the REST API.


Expand Down