Index of every page on this site: llms.txt
All skills
rivet-dev avatar

/rivet-open-orange

@3b027b3 official
by Rivetrivet-dev/skills53 stars
14
Run it yourself

Run a Cloudflare Workers project on Rivet with OpenOrange, the orange CLI, and move its Durable Objects and D1 databases off Cloudflare. Use when asked to run, deploy, migrate, or roll back a Cloudflare Worker on Rivet or OpenOrange.

Use this Skill: https://skilld.dev/gh/rivet-dev/skills/rivet-open-orange

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesrollback.md

≈512 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Roll back the migration

Every rollback action changes production, so stop and ask before each one. Step numbers match references/migrate.md. Roll back in detail has the same table, with each case.

Last step done How to go back
2, prepare Delete wrangler.migrate.jsonc and .open-orange/migrate/.
3, prepared Worker on Cloudflare The user deploys the original config with wrangler deploy.
4, migration on in Orange No action: Orange has no user traffic.
5, D1 before moved Stop the command with Ctrl-C. Cloudflare still holds the current data.
5, D1 moved No automated way back. See After a D1 database moved.
6 or 7 Roll back the Durable Objects, below.
8, clean up None. The data on Cloudflare is old.

Roll back the Durable Objects

  1. The user points the domain back at Cloudflare.

  2. For a Worker with crons, stop them on Orange, which rolls the pool, and the user adds them back on Cloudflare, for example with wrangler deploy --config wrangler.migrate.jsonc:

    rivet cluster env set --env ORANGE_CRONS=off --pool <pool>
  3. The user sets MIGRATOR_DISABLED to true on the prepared Worker:

    wrangler secret put MIGRATOR_DISABLED --config wrangler.migrate.jsonc

Done when every object serves on Cloudflare again, from its state when it moved, with its alarm. A busy object can refuse requests for up to 5 minutes. Tell the user that writes made on Orange stay on Orange.

MIGRATOR_DISABLED does not change D1. A moved D1 database stays on Orange, and Cloudflare still forwards its queries, so Orange keeps running with both step 4 settings.

After a D1 database moved

Orange holds the only current copy, and the copy on Cloudflare refuses every write. Keep the prepared Worker on Cloudflare: the original Worker reads old data, and its writes fail. To serve the database from Cloudflare again, the user copies the data back.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    This skill facilitates the migration of Cloudflare Workers to Rivet using the OpenOrange CLI. It involves installing vendor-provided tools, managing Cloudflare and Rivet credentials through environment variables, and executing deployment commands. The skill follows secure practices by ensuring the user manages secret values directly and avoids logging them.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

Signed by skilld at 3b027b3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last week

README badge

README badge for rivet-dev/skills/rivet-open-orange