Skip to content
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

Jump to bottom

Fix link in docs #173

Merged
merged 1 commit into from
Aug 19, 2023
Merged

Fix link in docs #173

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
5 changes: 3 additions & 2 deletions docs/how-to/how-to-startup-API.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,9 @@ using port 9999.
The configuration parameters are passed to `Teapot` so you can configure here
any of the options accepted by `Teapot` or `Zinc` servers. The `operations`
key is mandatory, and it's used for the plugin system of Stargate. See [the
operations and plugins documentation](Operations.md) to get a list of valid
options. For deployment environments, the `jwt` authentication scheme is recommended.
operations and plugins documentation](../reference/Operations.md) to get a list
of valid options. For deployment environments, the `jwt` authentication scheme
is recommended.

`#serverUrl` parameter is used as the base URL in the media controls. So, if
you're deploying your API behind a proxy and using a specific domain, this
Expand Down
Loading