Skip to content

fix: update clone instructions and SDK dependencies for all examples#362

Open
Nitin-kumar-yadav1307 wants to merge 4 commits into
geturbackend:mainfrom
Nitin-kumar-yadav1307:fix/template-clone-instructions
Open

fix: update clone instructions and SDK dependencies for all examples#362
Nitin-kumar-yadav1307 wants to merge 4 commits into
geturbackend:mainfrom
Nitin-kumar-yadav1307:fix/template-clone-instructions

Conversation

@Nitin-kumar-yadav1307

@Nitin-kumar-yadav1307 Nitin-kumar-yadav1307 commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

fix #360

Overview

This PR fixes the template setup instructions in the urBackend dashboard and example READMEs to ensure users can reliably fetch and run the selected examples from a clean clone.

Problem Statement

The source-based template workflow had inconsistent setup instructions:

  • Python SDK Demo README missing the cloned repository directory in cd path
  • Social Demo README using wrong repository URL (yash-pouranik/urBackend instead of geturbackend/urBackend)
  • Kanban Board README missing clone instructions entirely
  • Kanban server depending on local SDK path (file:../../../sdks/urbackend-sdk) which doesn't work outside the monorepo
  • Dashboard template cards showing inconsistent paths that didn't match actual repository structure

Solution

Updated all example READMEs and dashboard metadata to use consistent, correct clone instructions with the canonical repository URL and proper directory paths.

Files Changed

1. examples/python-sdk-demo/README.md

Change: Added urBackend/ prefix to cd path

- cd examples/python-sdk-demo
+ cd urBackend/examples/python-sdk-demo

2. examples/social-demo/README.md

Changes:

  • Fixed repository URL to canonical https://github.com/geturbackend/urBackend.git
  • Added urBackend/ prefix to clone path
  • Updated documentation link to geturbackend/urBackend
- git clone https://github.com/yash-pouranik/urBackend.git
- cd examples/social-demo
+ git clone https://github.com/geturbackend/urBackend.git
+ cd urBackend/examples/social-demo

3. examples/sdk-kanban/README.md

Change: Added clone instructions with correct path

+ ### 1. Clone the Repository
+ 
+ ```bash
+ git clone https://github.com/geturbackend/urBackend.git
+ cd urBackend/examples/sdk-kanban
+ ```
+ 
+ ### 2. Dashboard Setup

4. examples/sdk-kanban/server/package.json

Change: Replaced local file dependency with published package

- "@urbackend/sdk": "file:../../../sdks/urbackend-sdk",
+ "@urbackend/sdk": "0.4.2",

5. apps/web-dashboard/src/pages/Templates.jsx

Change: Updated all template README blocks with correct clone + cd instructions

  • React SDK Demo: Added clone instructions with urBackend/examples/react-sdk-demo path
  • Kanban Board: Added clone instructions with server/client setup
  • Python SDK Demo: Added clone instructions with urBackend/examples/python-sdk-demo path

Acceptance Criteria

All clone instructions use canonical repository URL

  • All examples now use https://github.com/geturbackend/urBackend.git

All cd paths include cloned repository directory

  • All paths follow pattern: cd urBackend/examples/<template-name>

Kanban setup succeeds without local SDK dependency

  • Server now uses published @urbackend/sdk@0.4.2 instead of local file reference

Template cards and READMEs describe the same workflow

  • Dashboard expanded READMEs match actual README files in each example

Users can follow instructions from clean shell after cloning

  • All paths are absolute from the cloned repository root

Testing

  • Verified all README files have correct clone URLs
  • Verified all cd paths include urBackend/ prefix
  • Verified Kanban server uses published SDK version
  • Verified dashboard template cards show consistent instructions

Related Issues

Summary by CodeRabbit

  • Documentation
    • Clarified setup instructions for React SDK, Kanban Board, Python SDK, and social demo templates.
    • Added repository cloning steps and improved command sequences for installation, configuration, and local development.
    • Expanded Kanban Board guidance for server/client startup, authentication, collections, and security settings.
    • Updated repository and documentation links across example projects.
    • Updated the Kanban example to use the published SDK package.

- Python SDK Demo README: add urBackend/ prefix to cd path
- Social Demo README: fix repo URL to geturbackend/urBackend, add urBackend/ prefix
- Kanban README: add clone instructions with urBackend/ prefix
- Kanban server: replace file: SDK dependency with published 0.4.2
- Templates.jsx: update all readme blocks with correct clone + cd instructions
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@Nitin-kumar-yadav1307, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 612c6de9-242c-4fad-b51d-1badb0adf23d

📥 Commits

Reviewing files that changed from the base of the PR and between 73e6d36 and 6d932db.

📒 Files selected for processing (2)
  • apps/web-dashboard/src/pages/Templates.jsx
  • examples/sdk-kanban/README.md
📝 Walkthrough

Walkthrough

Updates local setup instructions for React, Kanban, Python, and Social examples, aligns repository and documentation links with the canonical repository, and changes Kanban to use the published SDK version 0.4.2.

Changes

Template setup workflow

Layer / File(s) Summary
Example setup paths and dependency
examples/python-sdk-demo/README.md, examples/sdk-kanban/README.md, examples/sdk-kanban/server/package.json, examples/social-demo/README.md
README commands now use cloned repository paths and canonical links; Kanban setup adds cloning instructions and uses the published SDK package.
Dashboard template setup instructions
apps/web-dashboard/src/pages/Templates.jsx
Embedded React, Kanban, and Python setup instructions now include explicit clone, installation, startup, and configuration steps.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related issues

Possibly related PRs

Suggested reviewers: yash-pouranik

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: setup instructions and SDK dependency updates across the examples.
Linked Issues check ✅ Passed The README and dashboard updates match the required setup-flow fixes, canonical links, and Kanban SDK dependency change.
Out of Scope Changes check ✅ Passed The changes stay focused on example setup instructions, docs consistency, and the Kanban dependency fix.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/web-dashboard/src/pages/Templates.jsx`:
- Around line 58-59: Update the Terminal 2 startup instructions in the Templates
page so they first navigate to the urBackend/examples/sdk-kanban example
directory, then install dependencies and start the client; preserve the existing
client startup commands.
- Around line 62-63: Update the setup instructions in Templates.jsx to document
the complete Kanban schema from examples/sdk-kanban/README.md, including
required fields for the boards and tasks collections and RLS configured with
ownerField=ownerId. Keep the existing Auth and collection setup steps while
making the schema and ownership settings explicit enough for the app’s CRUD
operations.
- Around line 55-64: Update the Kanban setup instructions around the
server/client startup commands to configure environment variables first:
document both server/.env.example and client/.env.example, including
VITE_URBACKEND_PK and URBACKEND_SECRET_KEY, and instruct users to create the
corresponding .env files before running npm install and npm start/dev. Mention
that Vite-loaded environment changes require restarting the client server.

In `@examples/sdk-kanban/README.md`:
- Around line 12-19: Renumber the README setup headings following “Dashboard
Setup” so “Environment Variables” becomes step 3 and “Installation & Run”
becomes step 4, preserving the existing heading text and sequence.
🪄 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: da07707e-6187-420a-a389-13fc30ca9ba2

📥 Commits

Reviewing files that changed from the base of the PR and between a251cf3 and 73e6d36.

📒 Files selected for processing (5)
  • apps/web-dashboard/src/pages/Templates.jsx
  • examples/python-sdk-demo/README.md
  • examples/sdk-kanban/README.md
  • examples/sdk-kanban/server/package.json
  • examples/social-demo/README.md

Comment thread apps/web-dashboard/src/pages/Templates.jsx Outdated
Comment thread apps/web-dashboard/src/pages/Templates.jsx Outdated
Comment thread apps/web-dashboard/src/pages/Templates.jsx Outdated
Comment thread examples/sdk-kanban/README.md
- Environment Variables: step 3 (was incorrectly labeled as 2)
- Installation & Run: step 4 (was incorrectly labeled as 3)
…tails

- Add environment variable configuration steps (server/.env and client/.env)
- Document complete collection schemas with RLS settings
- Add note about Vite requiring server restart for env changes
- Clarify client startup runs from urBackend/examples/sdk-kanban

## Setup
\`\`\`bash
git clone https://github.com/geturbackend/urBackend.git

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Useparticular folder cloning.

1. Clone the repository without downloading the files

git clone --no-checkout --depth 1 <repository_url> <destination_folder>

2. Enter the repository directory

cd <destination_folder>

3. Enable sparse-checkout in cone mode

git sparse-checkout init --cone

4. Specify the folder you want to clone

git sparse-checkout set <path/to/desired/folder>

5. Download the files

git checkout main

- Add Option 1: Full Clone (existing method)
- Add Option 2: Sparse Checkout (recommended for faster setup)
- Sparse checkout clones only the template folder without full repo
@Nitin-kumar-yadav1307

Copy link
Copy Markdown
Collaborator Author

@yash-pouranik

Comment on lines 26 to 27
cd urBackend/examples/react-sdk-demo
npm install

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

You can add the same for all the examples na?
@Nitin-kumar-yadav1307

@yash-pouranik

Copy link
Copy Markdown
Member

@Nitin-kumar-yadav1307

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.

Provide reliable local setup flows for monorepo templates

2 participants