cf-orbs 0.2.6

Added

• cf-orbs status <orb> shows disk image: the image the orb's disk came from, and whether it is older than the image now deployed under that key. A paused orb that restores after cf-orbs upgrade or a deploy with a new digest keeps its old disk content; this shows it. A handle saved before this version has no image ref and shows unknown.

Fixed

• cf-orbs upgrade warned that paused orbs may not restore after an upgrade. They do restore (R18); the warning now says they keep the old disk content and that new image content reaches only orbs started from the image.

cf-orbs 0.2.5

Fixed

• New threads did not start on an install whose provider container had become slow. A spawn that takes 1 s took the dispatch program more than 90 s, Amp timed out after 300 s and sent the spawn again with a new token, and the orb never got its setup requests. The cause of the slow container is not known: it had run for 7 days, and a new lite container handled 10 spawns at once and 200 jobs in 15 min in tests. Three changes make the provider safe against it:
  • Watchdog: every 5 min the Worker asks the provider container to run true. If it does not answer in 5 s two times in a row, the Worker restarts the container. No check in the first 10 min after a start, and at most one such restart in 30 min.
  • dispatch.sh starts 2 processes for a job that is already done (was about 25). It reads the Worker's new plain-text replies (?format=text) with shell builtins and needs only sh, curl and sleep (no awk or sed).
  • The Worker sends progress lines in groups, so dispatch polls less often.
• /v1/status no longer waits on a provider container that does not answer. The log read stops after 5 s and the log tail says so. Before, one slow read blocked cf-orbs status, cf-orbs doctor, cf-orbs logs --provider and the 5-min provider check.

Added

• Config providerInstance: size of the provider container, "lite" (default), "standard-1" or "standard-2". cf-orbs deploy restarts a running provider when the size changes.
• cf-orbs doctor fails the provider check when the provider container runs but does not answer a log read.
• GET /v1/ops/<id> and POST /v1/orbs/<orb>/ops accept ?format=text. The JSON replies are unchanged, so an older dispatch.sh on an external host keeps working.

Changed

• External provider hosts: copy the new dispatch/dispatch.sh after you deploy the Worker. The new script needs a Worker from 0.2.5 or later.

cf-orbs 0.2.4

Added

• init --adopt: take over a Worker of the same name that this folder did not create. A new control token replaces the old one, and this folder's config and image/ are deployed. init prints one warning.

Fixed

• init in a folder with no saved deployment and no control token now stops when a Worker of the same name already exists in the account. Before, it deployed over that Worker: new control token, default config and image, old image keys dropped. The check runs wrangler deployments list --json --name <name> before any token, secret or deploy, in every mode. If the check cannot run, init warns and goes on. A rerun in the same folder is not checked. Neither is a folder that has .cf-orbs/control-token (a run that failed before it saved the URL, or a restored backup): it keeps the same token. Restoring on a new machine without the control token needs --adopt.

cf-orbs 0.2.3

Changed

• The default Amp provider name is cloudflare, not cf-orbs. The order is --provider-name, AMP_ORB_PROVIDER_NAME, the saved name, then cloudflare. A second install with its own Worker name no longer takes that name as its provider name: pass --provider-name. The Worker name default is still cf-orbs.

Added

• init prints one back up: line before the final amp command. It names the files to keep and links the guide.
• README: a Back up section. Docs: Back up and restore.

cf-orbs 0.2.2

Changed

• The init token prompt names the Amp page where you create the token: Amp Settings → Orbs → Add Provider.
• init warns when the provider name is not given explicitly, that is, when it comes from the config name or the default cf-orbs. The name must match the one in Amp. A name from --provider-name, AMP_ORB_PROVIDER_NAME or a previous run gives no warning.
• init --help lists the full provider-name fallback order.
• The comments in image/Dockerfile, provider/Dockerfile, provider/entry.sh and dispatch/dispatch.sh no longer contain internal requirement codes. init copies these files into your project.

Docs

• cf-orbs.config.example.jsonc lists debugExec, inactivityTimeoutMinutes, alarmSeconds and ampImageDigest.
• README: instance.vcpu accepts fractions between 1 and 4. The README links the docs site.

cf-orbs 0.2.1

Fixed

• cf-orbs doctor read the provider Dockerfile from the CLI templates only. In a source checkout before npm run build that file does not exist, so the check failed. It now reads the source file in that case. 0.2.0 was tagged but not published because of this test failure.

cf-orbs 0.1.1

Fixed

• package.json bin path has no ./ prefix, so npm no longer warns when it publishes.