Skip to content

feat(blog): add Volcano, built on Volcano post - #240

Open
marckong wants to merge 2 commits into
mainfrom
blog/volcano-built-on-volcano
Open

marckong wants to merge 2 commits into
mainfrom
blog/volcano-built-on-volcano

Conversation

@marckong

Copy link
Copy Markdown
Contributor

Tracking

None.

Why

New users can't see that volcano.dev itself runs on Volcano. This post shows it, from the people who built it.

Summary

  • Adds content/blog/volcano-built-on-volcano.md (category engineering, author Mark Kim, published 2026-11-19).
  • Adds a stack diagram at public/blog/volcano-built-on-volcano/stack.png. The diagram shows the web app and docs on Frontends; the REST, billing, and support APIs and the Stripe webhook on Functions; billing data in a Volcano database; and billing jobs on the scheduler.
  • The post has no cover, so its card shows the category icon. meta.json already picks up new posts through ....

Verification

  • pnpm lint:docs content/blog passes: docs OK.
  • pnpm check:links passes: links OK, 221 routes checked.
  • pnpm build passes, including search-index and server-trace checks; /blog/volcano-built-on-volcano is generated.

🤖 Generated with Claude Code

How volcano.dev runs on its own platform: the web app and docs site on
Frontends, the REST, billing, and support APIs and the Stripe webhook on
Functions, billing data in a Volcano database, and billing jobs on the
scheduler. Includes a stack diagram.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings November 19, 2026 16:05

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

@github-actions

github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

AI review: no P0-P2 findings

Reviewed 4fc6811. Run log

This PR adds an engineering blog post, "Volcano, built on Volcano", with a stack diagram, and lists it in content/blog/meta.json after the launch post. It changes only content and is low risk. Both earlier findings are fixed at this head. The post now sits before the October sandbox post in meta.json. The billing jobs are now called scheduled function invocations, with a working link, and the "four primitives" wording is gone. One small mismatch remains: the diagram still draws the scheduler as a separate primitive.

⚪ P3

  • public/blog/volcano-built-on-volcano/stack.png Diagram still shows Scheduler as its own primitive, unlike the revised text

Not checked: The AI review read the diff, the code, and the PR's text; it ran no tests or builds and read nothing outside this repository.

  • Whether volcano.dev's production web app, docs, APIs, Stripe webhook, billing database, and billing jobs really run on the Volcano primitives the post names.
  • How the post and its diagram look on /blog, /blog/category/engineering, and the post page, including the category-icon card shown when a post has no cover.
  • Confirm that production hosting, APIs, billing data, and billing schedules match the architecture described in the post.
  • Verify the rendered article, diagram, and listing card on the blog and engineering category page.

Human review: not needed

category: engineering
tags: [frontends, functions, database]
author: Mark Kim
published: "2026-11-19"

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.

🟡 P2: New post will be listed after the older October post, so /blog is no longer newest first

BlogHome says the listing is "newest first" (src/components/blog-home.tsx:9). But getSectionPages (src/lib/sections.ts:60) and the category pages order posts only by navigation order from content/blog/meta.json. That file lists introducing-volcano-agent-cloud (2026-11-19) and introducing-volcano-sandbox (2026-10-19) by name, then "...". This post is picked up only through "...", so it comes last: below the October sandbox post on /blog, on /blog/category/engineering, and in the sidebar, even though it's dated 2026-11-19. To fix it, add "volcano-built-on-volcano" to meta.json before "introducing-volcano-sandbox". Put it after the launch post if that post should stay first among the same-day posts.

Found by claude-opus-5-5

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 4fc6811: meta.json now names this post after the launch post and before the October sandbox post.


Some of volcano.dev's most critical data sits in Volcano's own [database](/platform/databases/overview). Billing is the part where a mistake costs real money.

The Volcano scheduler runs our critical billing operations. Those jobs don't run on an outside cron service. They run on the same scheduler you'd use for your own jobs.

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.

⚪ P3: Calls the scheduler a fourth primitive, but the docs treat it as part of Functions, and it has no link

The caption (line 18), this section, and line 44 call Frontends, Functions, the database, and the scheduler "four primitives". The diagram shows Scheduler as its own primitive box. The platform docs present cron scheduling as a Functions feature: content/platform/functions/scheduled-invocations.md, "Scheduled invocations" under Functions in content/platform/index.md, and the function-schedulers API reference. A reader looking for a separate scheduler product won't find one. Frontends, Functions, and the database each get a link, but the scheduler doesn't. Link /platform/functions/scheduled-invocations here, and consider describing it as Functions' scheduled invocations rather than a separate primitive.

Found by claude-opus-5-5

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 4fc6811: billing jobs are now described as scheduled function invocations with a link to /platform/functions/scheduled-invocations, and the "four primitives" wording is gone.

Name the post in meta.json after the launch post so /blog stays newest
first. Describe billing jobs as scheduled function invocations, link that
page, and drop the "four primitives" count.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

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

2 participants