Repository navigation
Conversation
…Hyperdrive CLOUD_DATABASE_URL replaces the PlanetScale database, roles and credentials with a database the deployer runs; the deploy migrates it as that URL's user. CLOUD_DATABASE_HYPERDRIVE=true puts a Hyperdrive configuration in front of it. Otherwise every consumer connects to the URL directly, as Neon test stages do. The deployed Worker reads both settings through Config, which Alchemy binds into each Worker that reads them at plan time. Without CLOUD_DATABASE_URL, production provisions PlanetScale behind Hyperdrive as before.
|
Warning Review limit reached
This review includes 3 billable files and costs up to $0.75.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 34 minutes for your next included review. View limit details
|
 |
Deploying Cloud to your own Cloudflare account required PlanetScale: the stack creates the database itself. Now you can point it at a Postgres database you already run, and choose whether to put Hyperdrive in front of it.
CLOUD_DATABASE_URL: the deploy migrates this database as the URL's user, uses it asDatabaseUrl, and creates no PlanetScale resources.CLOUD_DATABASE_HYPERDRIVE=true: also creates theDatabaseConnectionHyperdrive config, capped byCLOUD_DATABASE_CONNECTION_LIMIT. Without it, consumers connect directly, as Neon test stages do.CLOUD_DATABASE_URL, nothing changes.The deployed Worker makes the same choice because Alchemy binds the settings a Worker reads at deploy into its env, as it does for
TEST_STAGE_DATABASE_PROVIDER.Proved by
bun run checkand an offline stack evaluation (resources declared, nothing applied):DatabaseUrl.Replaces #1.
Reviewed with sol-loop: 1 round with gpt-6.1-sol on high. Sol verdict: approved
Created with Claude Opus 5.5 in Claude Code; reviewed by GPT-6.1 Sol in Codex.
🤖 Generated with Claude Code