fix(orchestrator): correct the deploy guidance — CF Workers Builds, no deco Admin flow - #333
Merged
Merged
Conversation
…o deco Admin flow #332 invented an "admin.deco.cx -> Sites -> New Site" step that does not exist. The real setup is one manual step: create a Workers & Pages app in the CF dash pointed at the repo. Also grounds the wrangler.jsonc guard in what the template actually ships: real deco-account resources (account_id, DECO_KV/SITES_KV ids, deco-otel-tail), not placeholders — which is why stripping them to force a local deploy publishes to whatever account the local token owns. Adds the missing rename step: the copied template keeps name/DECO_SITE_NAME as "storefront-tanstack" and template-bootstrap never changed them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
JonasJesus42
force-pushed
the
plugin-deco-app-setup-guide
branch
from
September 2, 2026 18:45
09ad339 to
4305f61
Compare
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.
Follow-up to #332, which I got wrong.
What #332 got wrong
It added a Step 1 telling the user to go to
admin.deco.cx→ Sites → New Site. That flow does not exist — I inferred it from the symptom instead of checking, and it would have sent every non-dev user hunting for a page that isn't there.It also described
account_id/DECO_KV/SITES_KV/deco-otel-tailas "placeholders that become valid after registration". They aren't placeholders.deco-sites/storefront-tanstack'swrangler.jsoncships real resources in deco's CF account:That distinction matters: a local
wrangler deployfails because the CLI isn't in that account, and deleting the keys until it succeeds is exactly what publishes the client's site onto whatever account the local token happens to own.What this PR does
wrangler deploy— now with the real reason.template-bootstrapsays "copy the tree, re-init git" and never touchesname/DECO_SITE_NAME, so every migrated site currently deploys claiming to bestorefront-tanstack. Found while verifying the above; shout if you'd rather split it out.🤖 Generated with Claude Code
Summary by cubic
Fixes the migration orchestrator's deploy instructions so users set up Cloudflare Workers Builds directly, instead of following a nonexistent deco Admin site flow.
admin.deco.cx→ Sites → New Site step; connecting the repo in the Cloudflare dashboard is now the one manual setup step.storefront-tanstackto the site slug inwrangler.jsonc.account_id,DECO_KV,SITES_KV, anddeco-otel-tailare real resources in deco's Cloudflare account, and deleting them to force a localwrangler deploycan publish the site to whatever account the local token owns.Written for commit 09ad339. Summary will update on new commits.