Repository navigation
Conversation
The playground runner's Fly app was shut down on 2026-10-29. Production turbolang.dev now answers /api/playground/run with the "not configured" 503, and /play shows the local CLI command. Remove the runner's fly.toml and the Fly deploy steps, say the runner is not deployed, and keep the steps for wiring a runner into Vercel. Drop the test assertions that pinned the Fly config. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The playground runner's Fly app was shut down on 2026-10-29. The docs still told people to deploy it to Fly and pointed at its old
fly.devURL. This PR says the runner is not deployed, removes its Fly config, and keeps the generic steps for wiring a runner into Vercel.fly apps listhas noturbolang-playground-runnerdig +short turbolang-playground-runner.fly.devreturns nothingcurl -X POST https://turbolang.dev/api/playground/runreturns 503 with "Hosted execution is not configured yet". That text comes fromrunnerUnavailableResult(), which the proxy returns only when the runner URL or token is missing (website/src/lib/playground-runner.ts)curl -sI https://turbolang.devreturnsServer: VercelandX-Vercel-IdRemoved
website/playground-runner/fly.tomlwebsite/playground-runner/README.md, including theflyctlcommands and thefly.devrunner URLwebsite/README.mdfly.tomlassertions inwebsite/tests/bl14-playground-runner.test.mjs. They only pinned the deleted file.node --test tests/bl14-playground-runner.test.mjspasses, 12 of 12website/playground-smoke-utils.mjs, now "a deployed runner"Still mentions Fly, left for the owner
examples/deploy/fly/(Dockerfile, README,fly.toml,main.tb): a user-facing example of deploying a Turbo program to Fly.io. It says nothing about where Turbo itself runs.docs/serverless.md,examples/README.md,website/src/app/docs/examples/page.tsx: list that example as a deploy target for users.turbo/crates/turbo-codegen-cranelift/runtime/vendor/sqlite3.c: vendored SQLite, the word "fly" is unrelated.Left alone as history: 3 files
CHANGELOG.md,design/BACKLOG.md(the dated BL-14 "DONE 2026-07-06" note),design/REACH-ROADMAP.md.🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.