Running in Production
Make builds repeatable, choose the production runtime, and publish or integrate safely.
Keep the definition repeatable
Generate the Anybuild definition, review it, and keep it with the project when reproducibility matters. Pin provider versions through configuration or environment overrides instead of depending indefinitely on changing defaults.
Validate the production combination
Build and run with the same backend and runtime that production will use. Docker and Wasmer are independent selections.
anybuild plan . --docker --wasmeranybuild . --docker --wasmer --startPublish to Wasmer
anybuild . --wasmer-deploy \ --wasmer-app-owner YOUR_OWNER \ --wasmer-app-name YOUR_APPTo let another system perform the final publication, write deployment configuration instead.
anybuild . --wasmer-deploy-config deploy.jsonIntegrate another platform
A platform integration can call the CLI or the Rust SDK, inspect the structured ProjectPlan, and consume paths from BuildOutcome. The current Docker backend exports build artifacts; it does not produce or publish a general-purpose OCI application image.
Keep credentials outside the definition
Supply registry tokens and application secrets through the operation environment or platform secret store. SDK events redact values whose variable names indicate tokens, passwords, secrets, credentials, or API keys, but the values remain available to the child processes that need them.