Thanks to visit codestin.com
Credit goes to docs.wavedash.com

Skip to main content
The wvdsh dev command starts a local HTTPS development server that lets you test your game in the Wavedash sandbox environment before publishing.
Before running, make sure you’ve configured your wavedash.toml.

​
Usage

wvdsh dev
This:
  1. Reads your wavedash.toml configuration
  2. Starts an HTTPS server at https://localhost:7777
  3. Opens your game in the Wavedash sandbox environment
  4. Serves files from your upload_dir

​
Options

OptionDescription
-c, --config <PATH>Path to wavedash.toml (default: ./wavedash.toml)
--no-openDon’t open the browser automatically

​
Examples

Use a custom config file: 
wvdsh dev --config ./configs/wavedash.toml
Start without opening the browser: 
wvdsh dev --no-open

​
How it works

The dev server creates a local testing environment that mimics the production Wavedash platform:
1

Certificate generation

On first run, the CLI generates a self-signed SSL certificate and installs it in your system’s trust store. This enables HTTPS which is required for many browser APIs.
2

File serving

The server serves your game files from the upload_dir specified in your config. It automatically handles compression and content types.
3

Sandbox redirect

Your browser opens the Wavedash sandbox with your local server as the game origin. This lets you test SDK features with real backend services.

​
Certificate trust

The first time you run wvdsh dev, the CLI generates and installs a self-signed certificate:
PlatformCertificate location
macOSSystem Keychain
WindowsCertificate Store
Linux/usr/local/share/ca-certificates/
You may see a security prompt asking to trust the certificate. Accept it to enable HTTPS.

​
Certificate files

Certificates are stored in your config directory: 
~/Library/Application Support/gg.wavedash.cli/dev-server/
├── localhost-cert.pem
└── localhost-key.pem

​
Supported features

The local dev server supports:
  • CORS headers for wavedash.com domains
  • Compression (gzip, brotli) for applicable files
  • Content-Type detection for common file types
  • Pre-compressed files (.gz, .br extensions)

​
File serving

The server automatically:
  1. Locates your HTML entrypoint (searches for index.html, then any .html file)
  2. Serves files from your upload_dir
  3. Handles engine-specific files (Godot .pck, Unity .data, etc.)

​
Sandbox URL

When the dev server starts, it builds a sandbox URL with:
  • Your game metadata (org, game, branch slugs)
  • Local origin (https://localhost:7777)
  • Engine type and version
  • Entrypoint parameters
The URL format is: 
https://{game_slug}.sandbox.wavedash.com/sandbox/permission-grant?...

​
Stopping the server

Press Ctrl+C to stop the dev server. It will:
  • Shut down the HTTPS server
  • Clean up any temporary files
  • Display a summary of served requests