Skip to content

fix(docs): add missing server start steps to Quick Taste and Quick Start - #100

Merged
julpayne merged 2 commits into
mainfrom
fix/quick-taste-connection-refused
Aug 17, 2026
Merged

fix(docs): add missing server start steps to Quick Taste and Quick Start#100
julpayne merged 2 commits into
mainfrom
fix/quick-taste-connection-refused

Conversation

@julpayne

@julpayne julpayne commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Expands the Quick Taste on the homepage into a 4-step sequence: install SDK with [server,cli], start Ollama, start EvalHub, run evaluation
  • Adds a "Connect to EvalHub" step to the Quick Start guide before "Submit an Evaluation", explaining that an EvalHub service must be reachable and linking to Local Mode for local setup
  • Links to Quick Start and Local Mode guides from the Quick Taste for full details

Closes #69

Test plan

  • Verify the homepage Quick Taste renders the <Steps> component correctly in the Starlight preview
  • Confirm the Quick Start step numbering is 1-5 with the new step 3
  • Validate internal links resolve (/getting-started/quickstart/, /guides/local-mode/)

Made with Cursor

The Quick Taste on home.mdx jumped straight from pip install to
evalhub eval run with no mention of starting either a model server or
the EvalHub service, causing "connection refused" for new users.

- Expand Quick Taste into a 4-step sequence: install SDK with
  [server,cli], start Ollama, start EvalHub, run evaluation
- Add a "Connect to EvalHub" step to Quick Start before Submit
- Link to Local Mode guide for full configuration details

Closes #69

Assisted-by: Cursor
Signed-off-by: Julian Payne <julpayne@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@julpayne, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 65 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9c0cd0f0-4bfa-4cc1-bab4-0a950fb8e77e

📥 Commits

Reviewing files that changed from the base of the PR and between 2967698 and 1c1be81.

📒 Files selected for processing (2)
  • src/content/docs/getting-started/quickstart.mdx
  • src/content/docs/home.mdx

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

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown
PR Preview Action v1.8.1

🚀 View preview at
https://eval-hub.github.io/pr-preview/pr-100/

Built to branch gh-pages at 2026-08-14 14:17 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

Add explicit base_url configuration steps so readers don't hit
connection-refused errors. Home page now notes Ollama must stay running
in its own terminal. Quickstart splits Step 3 into Cluster/Local tabs
with server_config_file and base_url commands for each path.

Assisted-by: Cursor
Signed-off-by: Julian Payne <julpayne@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

@gnaulak-redhat gnaulak-redhat left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks

@julpayne
julpayne merged commit e6d9ac7 into main Aug 17, 2026
4 checks passed
@julpayne
julpayne deleted the fix/quick-taste-connection-refused branch August 17, 2026 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(local-run): quick-taste example fails with connection refused when evalhub service is not running

2 participants