deploy

Set the GCORE_API_KEY environment variable, then invoke the deploy skill with an optional app name. It builds the WASM binary via the FastEdge MCP server, uploads it, creates or updates the app through the FastEdge API, and verifies the deployed URL.

The skill detects Cargo.toml, builds with cargo build --release --target wasm32-wasip1, and uploads the resulting binary. It also lints Rust sources for stderr logging, since FastEdge captures stdout only, and blocks deploys that would produce invisible logs.

The skill detects AssemblyScript apps via asconfig.json, Rust apps via Cargo.toml, and JavaScript or TypeScript apps via package.json. The MCP build tool selects the appropriate compiler based on the entry file extension.

Yes, pass the --skip-tests flag to bypass the pre-deploy test check and the Rust stderr logging lint. The skill logs a warning that you are deploying at your own risk when this override is used.

The skill fetches the existing app and refuses the update if the runtime model differs, such as wasi-http versus proxy-wasm. If the type matches, it prompts you to update the existing app or choose an alternative kebab-case name.

Status 530 indicates invalid environment variables or binary issues, while 532 means the app is timing out and needs optimization or a plan upgrade. The skill's verification step reports these codes with suggested debugging actions.