Repository navigation
Frostbase - #81
Merged
Merged
Frostbase#81
Conversation
Nobody deploys apps through managed hosting, and Workers for Platforms is a paid dependency we no longer want to carry, so the console stops speaking to it: the registry entry and sidebar section, the hosting API proxy and OpenAPI module, the GitHub App push-to-deploy flow, deploy tokens (cfbd_) and the Actions OIDC bearer in the guard, and the D1 tables they owned. Existing app/deploy_token/github_* tables are left in place untouched; nothing reads them any more. The e2e stack loses its :8800 hosting server; the landing page lists four live primitives instead of five.
With hosting gone, bare `init` only links the directory to a console project (no subdomain claim), `deploy` is the wrangler path alone, and `secret` - which set secrets on hosted apps - is removed. `key` keeps working off the same cloudflarebase.json; older files that still carry app/vars/assets are read, not refused.
The console and CLI no longer reference it, so the package, its deploy workflows, its quality/release entries, and the docs describing hosting go too.
Cloudflare asked us to stop using a name built on their trademark (and rejected cfbase too), so the product becomes Frostbase on frostbase.dev: the console, docs, packages (@frostbase/*), CLI binary, env vars (FROSTBASE_*), agent manifests (frostbase.agent.json), and the repo links (frostbase-dev/frostbase). Nothing that already works is allowed to break on the way: - Service keys mint as fsb_; existing cfbs_ keys still verify (the stored digest covers the whole string, prefix included), and e2e asserts both prefixes reach the verifier. - The admin SDKs and CLI still read CLOUDFLAREBASE_* / CFBASE_* env vars, cloudflarebase.json, cloudflarebase.schema.jsonc and ~/.cloudflarebase, and follow a stored cloudflarebase.com origin to frostbase.dev. - cloudflarebase.com stays attached to the production console: pages 301 to the same path on frostbase.dev, while /api and /agents keep answering so integrations with a hard-coded base URL do not break. Both origins stay trusted by the auth and db agents meanwhile. - cdn.cloudflarebase.com stays on the storage worker as a serve-only alias (STORAGE_SERVE_DOMAIN_ALIASES), so stored object URLs resolve. Names that hold state keep their old spelling on purpose - D1 databases, Analytics Engine datasets, the deployed console worker names, the JWT issuer and the mail sender - see AGENTS.md. Regenerating the db agent's types also surfaced a stale file: REMOTE_CONFIG_CACHE_SECONDS had moved into wrangler config without a typegen, and its hand augmentation now conflicts, so it is dropped.
npm records the root package name in package-lock.json; leaving it at cloudflarebase would make the next install rewrite it as noise.
The account's workers.dev subdomain moved from cloudflarebase to frostbase, so the preview console now serves at cloudflarebase-com-preview.frostbase.workers.dev. The preview auth and db agents only trusted the old hostname, which refuses sign-in from the console until they are redeployed with the new one.
cloudflarebase-com and cloudflarebase-com-preview become frostbase-dev and frostbase-dev-preview (preview serves at frostbase-dev-preview.frostbase.workers.dev). The Workers themselves are renamed in the dashboard, which keeps their secrets, custom domains and Workers Builds connection; wrangler has no rename, and deploying under a new name would mint an empty Worker. Builds refuses a config whose name disagrees with the connected Worker, so the dashboard rename has to land before this is pushed. The preview agents trust the new preview origin.
Email sending is now onboarded on the frostbase.dev zone (MX, SPF, DKIM and DMARC records in place), so sign-in and invitation mail stops carrying the old domain in its From address.
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
1 participant
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.
No description provided.