-
Notifications
You must be signed in to change notification settings - Fork 20
Update server.md #45
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.
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
Update server.md #45
Conversation
Add exit_on_error description
WalkthroughThis pull request adds a new configuration option, Changes
Sequence Diagram(s)sequenceDiagram
participant Server
participant InitCmd
participant Logger/Handler
Server->>InitCmd: Execute on_init command
InitCmd-->>Server: Return result (success/failure)
alt on_init success
Server->>Server: Continue startup
else on_init failure
alt exit_on_error true
Server->>Logger/Handler: Terminate server
else exit_on_error false
Server->>Logger/Handler: Log error and continue
end
end
Poem
Tip 🌐 Web search-backed reviews and chat
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
plugins/server.md (1)
88-90: Clarify Behavior Override in the Hint BlockThe hint block now instructs users with the statement:
“Useon_init.exit_on_error: trueto stop RoadRunner ifon_initcommand fails.”To further improve clarity, consider explicitly stating that this setting overrides the default behavior (i.e., logging the error and continuing execution) when the
on_initcommand fails. This additional clarification will help prevent any confusion regarding the server's behavior when this option is enabled.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
plugins/server.md(2 hunks)
🔇 Additional comments (1)
plugins/server.md (1)
40-42: Document the Newexit_on_errorOption ClearlyThe addition of the
exit_on_errorconfiguration option under theon_initsection is well documented with a default value offalse. This makes it clear to users that they need to opt in (by setting it totrue) if they want RoadRunner to terminate on an initialization failure.
rustatian
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @AleksandrKosovS 👍🏻
Add
exit_on_errordescription.Schema: https://raw.githubusercontent.com/roadrunner-server/server/refs/heads/master/schema.json
Summary by CodeRabbit