docs(actors): sync from rivet-dev/actors - #52
Conversation
|
🚅 Deployed to the website-pr-52 environment in rivet-website
|
67528ec to
54dbbf4
Compare
![rivet-docs-sync[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
54dbbf4 to
5c70a9b
Compare
![the-company-company[bot]](https://avatars.githubusercontent.com/in/3874572?s=60&v=4){kind=small}
| - Your server routes requests to `registry.start()`, `registry.serve()`, or `registry.handler()` correctly. | ||
| - No middleware is modifying the request or response body. | ||
|
|
||
| ### `serverless_destination_blocked` |
There was a problem hiding this comment.
🔵 Low · The troubleshooting page repeats the same error section
This adds a second identical serverless_destination_blocked heading and remediation immediately after the first one. Readers see the same error twice, and the generated heading IDs/TOC acquire a redundant -1 entry. Keep a single section (the one at lines 100–106).
|
|
||
| - Your endpoint URL is publicly reachable, and is not an internal hostname or address. | ||
| - The URL scheme is `http` or `https`, and the URL does not embed credentials. | ||
| - If you are self-hosting and intentionally point runners at an address on your own network, set `outbound.allow_private_networks` to `true` in your engine config, or list the specific range in `outbound.allow_cidrs`. |
There was a problem hiding this comment.
🔵 Low · The new remediation uses retired deployment terms
This user-facing addition calls the control plane an “engine” and calls workers “runners,” both of which conflict with the site's required terminology. Say “control plane config” and “workers” so this guidance remains consistent with the rest of the website.
1 participant
Automated docs sync from
rivet-dev/actors@4f21c76.Do not edit
vendor/actors/here. Edit the docs inrivet-dev/actorsand this PR updates itself.