feat: finish demo

[chronark]

What does this PR do?

This PR adds deployment platform functionality with a dashboard UI for managing projects, branches, and versions. It includes:

• A new quickstart guide (QUICKSTART-DEPLOY.md) for setting up the deployment platform locally
• Dashboard UI pages for projects, branches, and versions management
• Docker configuration for the dashboard container
• Database schema updates for deployment-related entities (projects, branches, versions)
• Backend API endpoints for project and version management
• CLI improvements for version creation and deployment
• Local development setup with seeded workspace data

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How should this be tested?

• Follow the new QUICKSTART-DEPLOY.md guide to set up the deployment platform locally
• Create a project through the dashboard UI at http://localhost:3000/projects
• Deploy a version using the CLI with the provided workspace and project IDs
• Verify the deployment appears in the versions list at http://localhost:3000/versions
• Test branch management functionality at http://localhost:3000/projects/[projectId]/branches

Checklist

Required

• Filled out the "How to test" section in this PR
• Read Contributing Guide
• Self-reviewed my own code
• Commented on my code in hard-to-understand areas
• Ran pnpm build
• Ran pnpm fmt
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the Unkey Docs if changes were necessary

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7c0a1f2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Rate limit exceeded

@chronark has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 37 seconds before requesting another review.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8d81c67 and 7c0a1f2.

📒 Files selected for processing (46)

• QUICKSTART-DEPLOY.md (1 hunks)
• apps/dashboard/Dockerfile (1 hunks)
• apps/dashboard/app/(app)/projects/[projectId]/branches/page.tsx (1 hunks)
• apps/dashboard/app/(app)/projects/page.tsx (1 hunks)
• apps/dashboard/app/(app)/versions/page.tsx (1 hunks)
• apps/dashboard/lib/db.ts (1 hunks)
• apps/dashboard/lib/trpc/routers/index.ts (3 hunks)
• apps/dashboard/lib/trpc/routers/project/branches.ts (1 hunks)
• apps/dashboard/lib/trpc/routers/project/create.ts (1 hunks)
• apps/dashboard/lib/trpc/routers/project/index.ts (1 hunks)
• apps/dashboard/lib/trpc/routers/project/list.ts (1 hunks)
• apps/dashboard/lib/trpc/routers/version/index.ts (1 hunks)
• apps/dashboard/lib/trpc/routers/version/list.ts (1 hunks)
• deployment/04-seed-workspace.sql (1 hunks)
• deployment/Dockerfile.mysql (1 hunks)
• deployment/docker-compose.yaml (3 hunks)
• go/apps/ctrl/services/version/create_version.go (2 hunks)
• go/apps/ctrl/services/version/deploy_workflow.go (7 hunks)
• go/apps/ctrl/services/version/get_version.go (1 hunks)
• go/cmd/version/bootstrap.go (1 hunks)
• go/cmd/version/main.go (4 hunks)
• go/go.mod (0 hunks)
• go/pkg/db/branch_find_by_project_name.sql_generated.go (1 hunks)
• go/pkg/db/branch_insert.sql_generated.go (1 hunks)
• go/pkg/db/branch_upsert.sql_generated.go (1 hunks)
• go/pkg/db/models_generated.go (5 hunks)
• go/pkg/db/project_find_by_id.sql_generated.go (1 hunks)
• go/pkg/db/project_find_by_workspace_slug.sql_generated.go (1 hunks)
• go/pkg/db/project_insert.sql_generated.go (1 hunks)
• go/pkg/db/querier_generated.go (7 hunks)
• go/pkg/db/queries/branch_find_by_project_name.sql (1 hunks)
• go/pkg/db/queries/branch_insert.sql (1 hunks)
• go/pkg/db/queries/branch_upsert.sql (1 hunks)
• go/pkg/db/queries/project_find_by_id.sql (1 hunks)
• go/pkg/db/queries/project_find_by_workspace_slug.sql (1 hunks)
• go/pkg/db/queries/project_insert.sql (1 hunks)
• go/pkg/db/queries/route_find_by_version_id.sql (2 hunks)
• go/pkg/db/queries/route_insert.sql (1 hunks)
• go/pkg/db/route_find_by_version_id.sql_generated.go (3 hunks)
• go/pkg/db/route_insert.sql_generated.go (4 hunks)
• go/pkg/db/schema.sql (5 hunks)
• internal/db/src/schema/branches.ts (2 hunks)
• internal/db/src/schema/builds.ts (2 hunks)
• internal/db/src/schema/hostnames.ts (1 hunks)
• internal/db/src/schema/routes.ts (1 hunks)
• internal/db/src/schema/versions.ts (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 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.
  • @coderabbitai modularize this function.
• 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 11, 2025 7:56am
engineering	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 11, 2025 7:56am

[chronark]

• chore: formatting and linting #3514
• feat: finish demo #3502 👈 (View in Graphite)
• chore: remove old protos #3497
• feat: use spire for tls #3496
• feat: workflow calls metald to create and boot a vm #3495
• chore: move vmprovisioner protos to shared proto #3494
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏