Skip to content

Updating README.md with CLI local installation steps and Discord link#131

Open
mradfaber wants to merge 3 commits intomainfrom
mradfaber-patch-2
Open

Updating README.md with CLI local installation steps and Discord link#131
mradfaber wants to merge 3 commits intomainfrom
mradfaber-patch-2

Conversation

@mradfaber
Copy link
Copy Markdown
Contributor

@mradfaber mradfaber commented Apr 16, 2026

Summary by CodeRabbit

  • Documentation
    • Refreshed project introduction with quick-access links to live demo, SDK, and community resources
    • Enhanced "Get Started Locally" section with clearer setup instructions using npx create-spree-app@latest
    • Added interactive CLI configuration details and local environment setup requirements
    • Updated project description terminology

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Apr 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
storefront Ready Ready Preview, Comment Apr 16, 2026 2:58pm

Request Review

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 16, 2026

Warning

Rate limit exceeded

@mradfaber has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 31 minutes and 59 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 31 minutes and 59 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e98d5c96-c475-4668-af61-6764adccd1d7

📥 Commits

Reviewing files that changed from the base of the PR and between 9c12dc2 and d32e9bf.

📒 Files selected for processing (1)
  • README.md

Walkthrough

README.md updated with a new project introduction header containing navigation links, revised eCommerce terminology, and a "Get Started Locally" section documenting the create-spree-app CLI setup process with system requirements and local deployment expectations.

Changes

Cohort / File(s) Summary
Documentation Updates
README.md
Added top-of-README header with project intro and navigation links (live demo, SDK, docs, Discord, website, enterprise). Updated project description wording to "eCommerce". Replaced inline demo/docs/SDK line with "If you like… star" callout and new "Get Started Locally" section documenting npx create-spree-app@latest my-store CLI flow (full-stack vs backend-only options, optional sample data, Node.js 20+ and Docker requirements, local admin URL).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • Update README.md #128: Overlapping README.md documentation edits reworking the project intro and adding Live Demo, Quickstart, SDK, and Discord links.

Suggested reviewers

  • damianlegawiec

Poem

🐰 A rabbit hopped through readmes bright,
With links and headers, shiny and tight,
"Get Started" paths now clearly shown,
eCommerce gardens freshly sown,
Discord bells and docs alight! 🌙

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: updating README.md documentation with CLI installation steps and adding a Discord link, which are the primary modifications evident in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch mradfaber-patch-2

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 and usage tips.

Copy link
Copy Markdown

@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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 43: Update the README sentence to clearly map ports: state that port 3000
is typically the Spree backend (including /admin) and the Next.js storefront dev
server runs on port 3001 by default (so the storefront URL is e.g.
http://localhost:3001), and note that the CLI or environment may assign
different ports so users should check the output or .env for actual ports; amend
the line mentioning "http://localhost:3000/admin" to reflect this distinction
and mention both ports (3000 for Spree admin, 3001 for Next.js storefront) and
that ports can differ if already in use.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9399fbc7-ab06-4fb2-b5b9-b51d64c8ce48

📥 Commits

Reviewing files that changed from the base of the PR and between 7ebaaf3 and 9c12dc2.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
1. Choose Full-stack (Backend + Next.js Storefront) or Backend only
2. Optionally load sample data (products, categories, images)

Once complete, your store should be running at http://localhost:3000/admin. The port can be different if `3000` is already used on your system. You need to have Node.js 20+ and Docker running.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Clarify port information to avoid user confusion.

The statement "your store should be running at http://localhost:3000/admin" could be confusing in the context of a storefront README. Based on line 172, the Next.js storefront dev server runs on port 3001, while port 3000 typically hosts the Spree Commerce backend (including /admin).

Consider clarifying:

  • Port 3000 = Spree backend admin panel
  • Port 3001 (or different) = Next.js storefront
  • Or specify that the CLI may use different ports

This would help users understand what to expect after running the setup command.

📝 Suggested clarification
-Once complete, your store should be running at http://localhost:3000/admin. The port can be different if `3000` is already used on your system. You need to have Node.js 20+ and Docker running.
+Once complete, the Spree backend admin should be accessible at http://localhost:3000/admin and the storefront at http://localhost:3001 (ports may vary if already in use). You need to have Node.js 20+ and Docker running.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Once complete, your store should be running at http://localhost:3000/admin. The port can be different if `3000` is already used on your system. You need to have Node.js 20+ and Docker running.
Once complete, the Spree backend admin should be accessible at http://localhost:3000/admin and the storefront at http://localhost:3001 (ports may vary if already in use). You need to have Node.js 20+ and Docker running.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 43, Update the README sentence to clearly map ports: state
that port 3000 is typically the Spree backend (including /admin) and the Next.js
storefront dev server runs on port 3001 by default (so the storefront URL is
e.g. http://localhost:3001), and note that the CLI or environment may assign
different ports so users should check the output or .env for actual ports; amend
the line mentioning "http://localhost:3000/admin" to reflect this distinction
and mention both ports (3000 for Spree admin, 3001 for Next.js storefront) and
that ports can differ if already in use.

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