docs: fill Standby page gaps and cross-link related pages - #2944
Draft
TC-MO wants to merge 7 commits into
Draft
Conversation
Contributor
|
✅ Preview for this PR (commit |
raethlo
approved these changes
Sep 4, 2026
raethlo
left a comment
Contributor
There was a problem hiding this comment.
Small nits, otherwise LGMT
Comment on lines
+186
to
+188
| ```text | ||
| https://jane-doe--my-actor.apify.actor | ||
| ``` |
Contributor
There was a problem hiding this comment.
Alternatively you can also reference https://{actorId}.apify.actor
| https://jane-doe--my-actor.apify.actor | ||
| ``` | ||
|
|
||
| Unlike the [container web server](./container_web_server.md) URL, which changes with every run, the Standby URL stays the same for all runs of the Actor. You can share it publicly or hardcode it in applications that call the Actor: copy it from the **Standby** tab on the Actor's detail page rather than building it from the username and Actor name, because some Actors use a different hostname format. |
Contributor
There was a problem hiding this comment.
Suggested change
| Unlike the [container web server](./container_web_server.md) URL, which changes with every run, the Standby URL stays the same for all runs of the Actor. You can share it publicly or hardcode it in applications that call the Actor: copy it from the **Standby** tab on the Actor's detail page rather than building it from the username and Actor name, because some Actors use a different hostname format. | |
| Unlike the [container web server](./container_web_server.md) URL, which changes with every run, the Standby URL stays the same for all runs of the Actor. You can share it publicly or hardcode it in applications that call the Actor: copy it from the **Endpoints** tab on the Actor's detail page rather than building it from the username and Actor name, because some Actors use a different hostname format. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Standby developer page was missing the Standby URL contract (stable across runs, unlike the per-run web server URL) and never pointed readers to authentication, scaling, the web server schema, or actor.json, all of which are documented elsewhere; the web server schema page had a single inbound link repo-wide. This adds the URL semantics to the env vars reference and the Standby page, and cross-links the Standby, container web server, Actor definition, and actor.json pages so each hands readers to the right reference.