Target-aware wrapper over wrangler. On the cloudflare target (default)
every command is forwarded verbatim to wrangler; on local/mieweb the CLI
runs your unchanged worker on the Node host harness backed by the matching
adapters. See the root README for the full model.
mieweb [--target <cloudflare|local|mieweb>] <command> [...args]Build container images once, distribute them with skopeo (see container-plan.md).
Prerequisites: skopeo plus a builder — buildah (preferred) or docker.
brew install skopeo buildah # macOS
# apt/dnf install skopeo buildah # LinuxThe CLI reads the containers array in wrangler.jsonc (class → Dockerfile)
and the per-target registry block in mieweb.jsonc:
mieweb images build # build every containers[] image (buildah/docker)
mieweb images push --target mieweb # build + skopeo copy → registry, pin digests
mieweb images push # cloudflare target: delegates to `wrangler containers push`
mieweb images inspect CONVERTER # skopeo inspect by binding name or class name
mieweb images status # lockfile pins vs. what's live in the registry
mieweb registry login --target mieweb # skopeo login (writes authFile; password prompted, never argv)
mieweb registry logout --target mieweb- Naming:
docker://<registry.url>/<project>/<class_name lowercased>:<git short SHA>, plus alatestmoving tag.projectdefaults to the wrangler appname. - Lockfile: pushes pin the manifest digest per class per target in
.mieweb/images.lock.json(commit it — it's what makes deploys reproducible).mieweb images statusreports drift between the pin and the registry'slatest. - Auth: prefer
authFile(written bymieweb registry login) over inline credentials; secrets are never passed on the command line or logged. Harbor robot accounts (robot$project+name) are the expected CI identity. - Cloudflare: the managed registry is wrangler's job —
images pushon thecloudflaretarget hands off towrangler containers pushrather than reimplementing its auth with skopeo.