[Fix] Bulldozer Studio and SpaceTime DB port conflict

[nams1570]

Context

Bulldozer Studio is what we use for debugging and inspecting bulldozer tables. Due to a merge conflict, both bulldozer studio and spacetime db were made accessible via the same port, 8139 by default.

Summary of Changes

Moving the former to 8140. Now they are both visible.

Summary by CodeRabbit

• Chores
  • Updated the local development port for Bulldozer Studio from 8139 to 8140, including corresponding configuration adjustments.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
stack-auth-hosted-components	Ready	Preview, Comment	Apr 18, 2026 0:54am
stack-backend	Ready	Preview, Comment	Apr 18, 2026 0:54am
stack-dashboard	Ready	Preview, Comment	Apr 18, 2026 0:54am
stack-demo	Ready	Preview, Comment	Apr 18, 2026 0:54am
stack-docs	Ready	Preview, Comment	Apr 18, 2026 0:54am
stack-preview-backend	Ready	Preview, Comment	Apr 18, 2026 0:54am
stack-preview-dashboard	Ready	Preview, Comment	Apr 18, 2026 0:54am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: dad2e3d8-7774-4b32-b12f-019e718b724d

📥 Commits

Reviewing files that changed from the base of the PR and between 22ae47f and eae1f87.

📒 Files selected for processing (2)

• apps/backend/scripts/run-bulldozer-studio.ts
• apps/dev-launchpad/public/index.html

---

📝 Walkthrough

Walkthrough

Bulldozer Studio's port configuration is updated from 8139 to 8140 across both the backend server startup script and the dev launchpad UI reference, ensuring consistent port mapping for local development.

Changes

Cohort / File(s)	Summary
Bulldozer Studio Port Update apps/backend/scripts/run-bulldozer-studio.ts, apps/dev-launchpad/public/index.html	Updated port suffix from "39" to "40" in both the server startup configuration and the dev launchpad app entry, aligning the listening port and UI reference for Bulldozer Studio.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A rabbit hops through port configurations so neat,
From thirty-nine to forty, the transition complete!
The studio shifts, the server aligns,
New pathways emerge on these numbered lines. 🎯

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the main change: resolving a port conflict between Bulldozer Studio and SpaceTime DB by moving Bulldozer Studio to a different port.
Description check	✅ Passed	The description provides adequate context explaining the issue (port conflict), the solution (moving to port 8140), and the outcome (both services now visible). It follows a clear structure with Context and Summary of Changes sections.
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 docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch make-bs-studio-visible

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Resolves a local development port conflict where Bulldozer Studio and SpacetimeDB were both exposed on the same default port, by moving Bulldozer Studio to a new port so both services are accessible concurrently.

Changes:

• Update the dev-launchpad “Bulldozer Studio” service link to use port suffix 40 (i.e., 8140 with the default prefix).
• Update the backend Bulldozer Studio runner to listen on 8140 (with the default NEXT_PUBLIC_STACK_PORT_PREFIX).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
apps/dev-launchpad/public/index.html	Updates the Bulldozer Studio entry to point to port suffix 40 so the launchpad links to the new port.
apps/backend/scripts/run-bulldozer-studio.ts	Changes STUDIO_PORT to end in 40, moving the studio server off the conflicting 8139 port.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[greptile-apps]

Greptile Summary

This PR resolves a port conflict where Bulldozer Studio and SpacetimeDB were both assigned port 8139. Bulldozer Studio is moved to port 8140 by updating the STUDIO_PORT constant in run-bulldozer-studio.ts and the portSuffix in the dev launchpad HTML. The change is consistent across both files, and devcontainer.json already forwards both ports.

Confidence Score: 5/5

Safe to merge — minimal, targeted fix with no logic changes.

The change is a simple two-file port number update that correctly resolves the conflict. Both the server and the UI are updated consistently, devcontainer already exposes both ports, and there are no other references to the old port tied to Bulldozer Studio in the codebase.

No files require special attention.

Important Files Changed

Filename	Overview
apps/backend/scripts/run-bulldozer-studio.ts	Port suffix changed from "39" to "40" (STUDIO_PORT now resolves to 8140 by default), correctly separating Bulldozer Studio from SpacetimeDB at 8139.
apps/dev-launchpad/public/index.html	Bulldozer Studio portSuffix updated from "39" to "40" in the dev launchpad UI, consistent with the server script change.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    subgraph Before
        BS1["Bulldozer Studio\nport 8139 ❌"]
        ST1["SpacetimeDB\nport 8139 ❌"]
        BS1 -- "conflict" --- ST1
    end
    subgraph After
        BS2["Bulldozer Studio\nport 8140 ✅"]
        ST2["SpacetimeDB\nport 8139 ✅"]
    end

Loading

_{Reviews (1): Last reviewed commit: "fix: port conflict b/w bs and spacetime" | Re-trigger Greptile}