Reference for the two workflow commands you'll run day-to-day. Setup commands — wavedash auth * and wavedash update — live with Authentication and Installation.
Local development
wavedash dev
Starts a local HTTPS server at https://localhost:7777, serves files from upload_dir, and opens the Wavedash sandbox with SDK injection.
| Option | Description |
|---|---|
--config <PATH> | Path to wavedash.toml (default: ./wavedash.toml) |
--no-open | Skip launching the browser |
The first time you run wavedash dev, a self-signed certificate is installed. On macOS a fingerprint prompt will appear. On Linux/Windows, sudo or administrator privileges may be required.
The sandbox validates your SDK wiring locally. It does not replace a final smoke test of the uploaded build on Wavedash.
Build and push
wavedash build push
Uploads everything under upload_dir and registers a new immutable build for the configured game_id. Old builds stay available for rollback.
| Option | Description |
|---|---|
--config <PATH> | Path to wavedash.toml (default: ./wavedash.toml) |
-m, --message <TEXT> | Build description or changelog note |
Uploading does not publish the build — there is currently no CLI publish command. After the upload finishes, open the Developer Portal and promote the build when you're ready to make it live.
Verify config
Confirm game_id and upload_dir match your engine output.
Push
Run wavedash build push and wait for the new build ID.
Publish
Open the Developer Portal and promote the uploaded build.
Global options
These flags apply to every subcommand:
| Option | Purpose |
|---|---|
--version | Print CLI version |
--help | Show help for the command |
--verbose | Increase log detail |