Skip to content

Conversation

@tisnik
Copy link
Contributor

@tisnik tisnik commented Jul 30, 2025

Description

LCORE-248: Getting started guide, 3rd version

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up service version
  • Bump-up dependent library
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change
  • Unit tests improvement
  • Integration tests improvement
  • End to end tests improvement

Related Tickets & Documents

  • Related Issue #LCORE-248

Summary by CodeRabbit

  • Documentation
    • Expanded and restructured the "Getting Started" guide with comprehensive step-by-step instructions for local deployment of Llama Stack as a separate process.
    • Added detailed sections on prerequisites, tool installation, configuration, verification steps, and integration with LCS.
    • Updated the table of contents and improved organization for easier navigation.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 30, 2025

Walkthrough

The "Getting started" documentation was extensively expanded and reorganized, especially in the "Local deployment" section for running Llama Stack as a separate process. The update introduces detailed step-by-step instructions, new configuration examples, command outputs, and verification steps, transforming the guide into a comprehensive resource for local deployment and integration with LCS.

Changes

Cohort / File(s) Change Summary
Getting Started Documentation Overhaul
docs/getting_started.md
Major expansion and restructuring of the local deployment section, adding detailed setup steps, configuration examples, command outputs, verification procedures, and updated table of contents. Minor reordering and cleanup in other sections. No code changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

Poem

🐇
In docs anew, the steps unfold,
With commands and configs, clear and bold.
From setup deep to LCS start,
Each section guides with rabbit heart.
So hop along this local quest—
Your Llama Stack is now expressed!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@tisnik
Copy link
Contributor Author

tisnik commented Jul 30, 2025

/retest

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (2)
docs/getting_started.md (2)

12-20: Normalize ToC list indentation to satisfy markdown-lint MD007.

Current sub-items are indented with 8 spaces; GitHub-flavoured Markdown expects 4 (or 2) for a second-level list.

-* [Local deployment](#local-deployment)
-        * [Prerequisites](#prerequisites)
+* [Local deployment](#local-deployment)
+    * [Prerequisites](#prerequisites)

Apply the same 4-space indentation pattern for all nested ToC entries.
This keeps rendering consistent across Markdown engines and eliminates the linter warnings.


191-206: Add language identifiers to bare fenced blocks (MD040).

Several code / log excerpts open with plain ````` but no language hint, triggering MD040 and reducing syntax-highlighting:

-```
+```text
usage: llama [-h] ...

Repeat for the exception trace, server log, make run output and the final curl response block.

Affected opening fences start at lines 191, 212, 377, 559 and 578.

Also applies to: 212-228, 377-381, 559-563, 578-592

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ed855cc and 5b916c5.

📒 Files selected for processing (1)
  • docs/getting_started.md (3 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/getting_started.md

12-12: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


13-13: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


14-14: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


15-15: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


16-16: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


17-17: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


18-18: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


19-19: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


20-20: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


21-21: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


23-23: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


24-24: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


191-191: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


212-212: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


377-377: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


559-559: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


578-578: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build-pr

Comment on lines +12 to +18
* [Prerequisities](#prerequisities)
* [Installation of all required tools](#installation-of-all-required-tools)
* [Installing dependencies for Llama Stack](#installing-dependencies-for-llama-stack)
* [Check if Llama Stack can be started](#check-if-llama-stack-can-be-started)
* [Llama Stack configuration](#llama-stack-configuration)
* [Run Llama Stack in a separate process](#run-llama-stack-in-a-separate-process)
* [LCS configuration to connect to Llama Stack running in separate process](#lcs-configuration-to-connect-to-llama-stack-running-in-separate-process)
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Fix repeated typo – “Prerequisities” → “Prerequisites”.

The word is miss-spelled in both the ToC and section headers which also breaks generated anchor links.

-        * [Prerequisities](#prerequisities)
+        * [Prerequisites](#prerequisites)

-#### Prerequisities
+#### Prerequisites

-* [Prerequisities](#prerequisities-1)
+* [Prerequisites](#prerequisites-1)

-#### Prerequisities
+#### Prerequisites

Also applies to: 21-21, 94-100, 598-600

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

12-12: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


13-13: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


14-14: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


15-15: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


16-16: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


17-17: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


18-18: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)

🤖 Prompt for AI Agents
In docs/getting_started.md around lines 12 to 18, 21, 94 to 100, and 598 to 600,
the word "Prerequisities" is misspelled and should be corrected to
"Prerequisites" in both the table of contents and section headers. Update all
instances of this typo to fix the spelling and ensure that the generated anchor
links work correctly.

@tisnik tisnik merged commit 485affb into lightspeed-core:main Jul 30, 2025
17 of 19 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Aug 21, 2025
18 tasks
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.

1 participant