Skip to content

docs: Added deployment scenarios - #364

Merged
ilyabo merged 3 commits into
mainfrom
docs--Deployment-Scenarios
Feb 13, 2026
Merged

ilyabo merged 3 commits into
mainfrom
docs--Deployment-Scenarios

Conversation

@ilyabo

@ilyabo ilyabo commented Feb 13, 2026 •

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • Documentation
    • Added new Deployment Scenarios guide detailing five deployment models: browser-only analytics, browser clients with shared datasets, collaborative server-backed rooms, offline-capable PWAs, and desktop applications.
    • Included platform options reference and hybrid setup guidance.
    • Updated documentation sections with navigation references to deployment scenarios.

Signed-off-by: Ilya Boyandin <[email protected]>
Signed-off-by: Ilya Boyandin <[email protected]>
Signed-off-by: Ilya Boyandin <[email protected]>
@coderabbitai

coderabbitai Bot commented Feb 13, 2026 •

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This PR introduces comprehensive deployment scenario documentation for SQLRooms and integrates it into the site navigation. A new docs/deployment-scenarios.md file outlines five deployment models with platform options, while README.md and docs/overview.md are updated to reference this guidance. The site configuration adds a sidebar entry for the new page.

Changes

Cohort / File(s) Summary
Documentation Updates
README.md, docs/overview.md
Add references and links to new Deployment Scenarios page in the "Why Single-Node?" and "Next Steps" sections with minor spacing adjustments.
Navigation Configuration
docs/.vitepress/config.ts
Reorder imports and add new sidebar entry for Deployment Scenarios at /deployment-scenarios route under Introduction section.
New Deployment Guide
docs/deployment-scenarios.md
New comprehensive documentation covering five deployment models: browser-only analytics, browser with shared datasets, collaborative rooms with server, offline PWA, and desktop packaging; includes backend platform options and hybrid setup guidance.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Five paths unfold through SQLRooms' vast land,
From browser-only dreams to server grand,
PWAs, desktops, and rooms to share—
The docs now guide you everywhere! 🚀

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title accurately describes the primary change: adding comprehensive deployment scenarios documentation across multiple files and the config.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs--Deployment-Scenarios

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.

@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: 2

🤖 Fix all issues with AI agents
In `@docs/deployment-scenarios.md`:
- Line 91: Update the Query PWA example link that currently uses "tree/HEAD" so
it matches the rest of the document by using "tree/main" instead; locate the
link text "[Query PWA
example](https://github.com/sqlrooms/examples/tree/HEAD/query-pwa)" and replace
"HEAD" with "main" to make the URL "[Query PWA
example](https://github.com/sqlrooms/examples/tree/main/query-pwa)".
- Line 109: Replace the inconsistent internal link URL
"/case-studies.html#foursquare-spatial-desktop" (anchor text "Foursquare Spatial
Desktop case study") with the extension-less path
"/case-studies#foursquare-spatial-desktop" to match the other internal links'
format; update the link target in the markdown so it uses
"/case-studies#foursquare-spatial-desktop" instead of including ".html".
🧹 Nitpick comments (1)
README.md (1)

36-36: LGTM — new links follow existing README convention.

The new Deployment Scenarios references are consistent with the existing link style and placement.

One minor note: all README links use http:// rather than https://. This is a pre-existing pattern across the file, so not something to block this PR, but worth addressing in a follow-up.

Also applies to: 58-59

Examples and references:

- [Offline Use](https://sqlrooms.org/offline-use)
- [Query PWA example](https://github.com/sqlrooms/examples/tree/HEAD/query-pwa)

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.

⚠️ Potential issue | 🟡 Minor

Inconsistent Git ref in link: HEAD vs main.

Line 61 uses tree/main for the sync example link, but line 91 uses tree/HEAD for the query-pwa example. Use main for consistency with the rest of the document.

Proposed fix
-- [Query PWA example](https://github.com/sqlrooms/examples/tree/HEAD/query-pwa)
+- [Query PWA example](https://github.com/sqlrooms/examples/tree/main/query-pwa)
📝 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
- [Query PWA example](https://github.com/sqlrooms/examples/tree/HEAD/query-pwa)
- [Query PWA example](https://github.com/sqlrooms/examples/tree/main/query-pwa)
🤖 Prompt for AI Agents
In `@docs/deployment-scenarios.md` at line 91, Update the Query PWA example link
that currently uses "tree/HEAD" so it matches the rest of the document by using
"tree/main" instead; locate the link text "[Query PWA
example](https://github.com/sqlrooms/examples/tree/HEAD/query-pwa)" and replace
"HEAD" with "main" to make the URL "[Query PWA
example](https://github.com/sqlrooms/examples/tree/main/query-pwa)".


Reference:

- [Foursquare Spatial Desktop case study](/case-studies.html#foursquare-spatial-desktop)

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.

⚠️ Potential issue | 🟡 Minor

Inconsistent internal link format: .html extension used here but not elsewhere.

Other internal links in this file (e.g., lines 23–24, 42) use extension-less paths like /examples#.... This one uses /case-studies.html. Consider dropping the .html for consistency.

Proposed fix
-- [Foursquare Spatial Desktop case study](/case-studies.html#foursquare-spatial-desktop)
+- [Foursquare Spatial Desktop case study](/case-studies#foursquare-spatial-desktop)
📝 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
- [Foursquare Spatial Desktop case study](/case-studies.html#foursquare-spatial-desktop)
- [Foursquare Spatial Desktop case study](/case-studies#foursquare-spatial-desktop)
🤖 Prompt for AI Agents
In `@docs/deployment-scenarios.md` at line 109, Replace the inconsistent internal
link URL "/case-studies.html#foursquare-spatial-desktop" (anchor text
"Foursquare Spatial Desktop case study") with the extension-less path
"/case-studies#foursquare-spatial-desktop" to match the other internal links'
format; update the link target in the markdown so it uses
"/case-studies#foursquare-spatial-desktop" instead of including ".html".

@ilyabo
ilyabo merged commit 8973d9f into main Feb 13, 2026
4 checks passed
@ilyabo
ilyabo deleted the docs--Deployment-Scenarios branch February 13, 2026 13:08
@coderabbitai coderabbitai Bot mentioned this pull request Mar 22, 2026
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