docs: clarify Parse Server cluster option

[jacog2]

Summary

• Add a Parse Server guide note explaining the cluster option.
• Clarify that cluster is CLI-only because the CLI starts the worker processes.
• Document true and numeric worker-count usage.

Closes #848.

Validation

• git diff --check
• Jekyll build not run locally: Ruby/Bundler are not installed in this environment.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation update adds the cluster Parse Server option to the usage guide, explaining that it enables Node.js cluster mode when launching via CLI, how workers are forked, and that it is not usable in the ParseServer constructor.

Changes

Parse Server Option Documentation

Layer / File(s)	Summary
cluster option documentation _includes/parse-server/usage.md	Adds cluster to the Parse Server options list with explanation of CLI-based cluster mode, worker forking behavior, and constructor incompatibility.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 6 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Engage In Review Feedback	❓ Inconclusive	Cannot verify review engagement. PR has only one commit with no amendments. GitHub reviews exist in the web interface, not git. Cannot assess if feedback was engaged.	Check GitHub PR #974 web page for review comments to verify user engagement with feedback.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title begins with 'docs:' prefix as required and clearly summarizes the main change: clarifying the Parse Server cluster option documentation.
Linked Issues check	✅ Passed	The pull request adds documentation explaining the cluster option as requested in issue #848, including behavior details and CLI-only usage notes.
Out of Scope Changes check	✅ Passed	The pull request contains only documentation updates to a single file directly addressing the cluster option explanation requirement from issue #848.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	Documentation-only change. No vulnerabilities, sensitive data exposure, or insecure patterns. CLI-only clarification prevents misconfiguration.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}