rivet-open-orange
Installation
SKILL.md
Run a Cloudflare Worker on Rivet with OpenOrange
OpenOrange runs a Cloudflare Workers project on Rivet with no changes to its code. orange dev runs it locally, orange deploy ships it to a Rivet cluster, and orange migrate moves its Durable Objects and D1 databases off Cloudflare while the app keeps serving.
Do the parts the user asks for. Each part needs the parts before it: set up, run locally, deploy, migrate.
Rules
- Stop and ask. At each Stop and ask, tell the user what changes and for whom, then wait for a yes. A yes covers that one action.
- Secrets. The user creates and types every secret value:
WORKER_MIGRATOR_TOKEN,CLOUDFLARE_API_TOKEN, and Rivet tokens. Write a secret only as its name or$NAME, in commands, files, and output. Ask the user to run each command that prompts for a value, such aswrangler secret putandrivet cluster secret set. - The code stays. Keep the app code and the Wrangler configuration as they are,
compatibility_flagsincluded: Cloudflare runs the same code until the migration ends. When a fix needs a code change, tell the user first. - Cloudflare stays. Orange deletes nothing on Cloudflare. The user deletes the Cloudflare Worker and its data, after the migration.
- Look it up.
orange <command> --helphas every flag, JSON event, and exit code. The Deploy and Migrate guides have every step, message, and failure in detail, and each binding has a page under https://openorange.dev/docs/bindings/. - Bugs. When a command ends with
Looks like a bug? Report it: <link>, give the user the link. Orange prints it only for unexpected errors.
Set up
- Install.
orange --versionprints a version when OpenOrange is installed. Otherwise: