Skip to content

Conversation

@Anxhela21
Copy link
Contributor

@Anxhela21 Anxhela21 commented Aug 6, 2025

Description

Extracted the library deployment section from getting_started.md into a new getting_started.md file. Renamed the original to deployment_guide.md.

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-229] Create a deployment guide
  • Closes #

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive deployment guide detailing multiple methods for deploying and configuring the Lightspeed Core Stack service, including local and containerized options, with step-by-step instructions and usage examples.
    • Simplified and condensed the getting started guide to focus solely on running the service with Llama Stack as an embedded Python library, providing a streamlined setup process for new users.

Signed-off-by: Anxhela Coba <acoba@redhat.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 6, 2025

Walkthrough

A new, comprehensive deployment guide for the Lightspeed Core Stack (LCS) was added, detailing multiple deployment methods and configurations. Simultaneously, the existing getting started guide was heavily simplified to focus only on local library-based deployment, removing container and advanced usage instructions.

Changes

Cohort / File(s) Change Summary
Deployment Guide Addition
docs/deployment_guide.md
Added a detailed deployment guide for LCS, covering local and containerized deployment, configuration, and usage.
Getting Started Simplification
docs/getting_started.md
Rewrote and condensed the getting started guide to focus only on local, library-based deployment, removing advanced and container instructions.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

Poem

In docs we hop, with guides anew,
From simple starts to stacks in view.
Containers, configs, YAML delight,
Now clearer paths for day and night.
With every hop, our docs expand—
Deploy with ease, just as we planned!
🐇✨

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.
  • 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.

Support

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

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.

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: 0

🧹 Nitpick comments (5)
docs/getting_started.md (1)

1-5: Heading level jumps from H1 to H3

The very first subsection uses ### even though there is no ## level heading in-between. This violates MD001 and looks odd in most renderers.

-### Llama Stack used as a library
+## Llama Stack used as a library
docs/deployment_guide.md (4)

5-28: Unordered-list indentation/style is inconsistent

The manually-written TOC mixes two-space and four-space indents and alternates between * and -. That triggers a large set of MD004 / MD007 warnings and makes the Markdown harder to maintain.

Consider regenerating the TOC with a plugin (or at least normalising to a single indent level and bullet style).
Example:

-* [Preface](#preface)
-* [Deployment methods](#deployment-methods)
+* [Preface](#preface)
+* [Deployment methods](#deployment-methods)
   * [Integration with Llama Stack framework](#integration-with-llama-stack-framework)
     * [Llama Stack as a library](#llama-stack-as-a-library)
     * [Llama Stack as a server](#llama-stack-as-a-server)

110-114: Wordiness – “last but not least”

Line 112 uses the phrase “last but not least”, which the LanguageTool style checker flags as verbose. A simpler alternative such as “finally” keeps the prose tighter.


1530-1535: Use “cannot” instead of “can not”

“Cannot” is the common spelling; splitting it is only needed for emphasis.
Fixing it removes the LanguageTool warning.

-... the standard port mapping can not be leveraged there ...
+... the standard port mapping cannot be leveraged there ...

218-244: Add language identifiers to fenced code blocks

Several fenced blocks (e.g. sample CLI output around lines 222, 408, 590, 1178) omit a language tag, triggering MD040.
Annotate them with text (or bash, json, etc.) so syntax highlighting and linting work correctly.

-```ascii
+```text
   Using CPython 3.12.10 interpreter at: /usr/bin/python3

Repeat for the other anonymous blocks.

Also applies to: 408-416, 590-598, 1174-1182

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 739b786 and eec8944.

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

3-3: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

docs/deployment_guide.md

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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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: 4; Actual: 8

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


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

(MD007, ul-indent)


71-71: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


72-72: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


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

(MD007, ul-indent)


73-73: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


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

(MD007, ul-indent)


74-74: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


75-75: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


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

(MD007, ul-indent)


76-76: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


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

(MD007, ul-indent)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


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

(MD040, fenced-code-language)


990-990: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


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

(MD040, fenced-code-language)

🪛 LanguageTool
docs/deployment_guide.md

[style] ~112-~112: ‘last but not least’ might be wordy. Consider a shorter alternative.
Context: ...ally made changes and improvements. And last but not least, it is possible to trace, monitor and d...

(EN_WORDINESS_PREMIUM_LAST_BUT_NOT_LEAST)


[grammar] ~978-~978: Ensure spelling is correct
Context: ...* image is needed and no other packages nor tools need to be installed. ### Retr...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~1533-~1533: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...container and the standard port mapping can not be leveraged there. This configuration ...

(CAN_NOT_PREMIUM)

⏰ 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: e2e_tests

@tisnik tisnik changed the title [LCORE-229] Create a deployment guide LCORE-229: Create a deployment guide Aug 6, 2025
Copy link
Contributor

@tisnik tisnik left a comment

Choose a reason for hiding this comment

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

LGTM!

@tisnik tisnik merged commit 8cc0ac7 into lightspeed-core:main Aug 6, 2025
18 checks passed
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.

2 participants