Deploying Apps

Waymaker Host uses a GitHub Actions build pipeline that compiles your code and deploys it to Cloudflare's global CDN — 330+ cities with sub-50ms latency.

How Deployment Works

1. Trigger — You push to your branch or manually trigger a deploy
2. Build Runner — GitHub Actions checks out your code, installs dependencies, and runs your build command
3. Upload — Build output is uploaded to Cloudflare's global CDN
4. Live — Your app is available at <slug>.waymakerapp.com within seconds

Automatic Deployments

When you create an app with a linked GitHub repo, pushes to the configured branch automatically trigger deployments. This is the recommended workflow:

git push origin main  # Triggers a build automatically

Manual Deployments

Trigger a deployment at any time:

CLI

waymaker host apps deploy <app-id>

MCP

"Deploy my customer-portal app"

Viewing Deployment History

See all deployments for an app:

waymaker host apps deployments <app-id>

Each deployment shows:

Field	Description
id	Unique deployment ID
version	Auto-incrementing version number
git_commit_sha	The commit that was deployed
git_commit_message	Commit message for context
status	building, success, failed
deployed_url	Live URL for this deployment
deployed_at	When the deployment went live

Build Configuration

Build Command

The command that compiles your app. Common examples:

Framework	Build Command	Output Dir
Next.js	npm run build	.next
React (Vite)	npm run build	dist
Vue	npm run build	dist
Astro	npm run build	dist
SvelteKit	npm run build	build

Environment Variables at Build Time

Environment variables set via host_app_env_set are available during the build process. This means your VITE_* or NEXT_PUBLIC_* variables are baked into the output.

After changing environment variables, you need to redeploy:

waymaker host env set <app-id> --var NEXT_PUBLIC_API_URL=https://api.example.com
waymaker host apps deploy <app-id>

Troubleshooting Builds

Build Fails Immediately

• Check that your GitHub repo is accessible to the Waymaker GitHub App
• Verify the repository_branch exists
• Check host_github_status to confirm the installation is active

Build Succeeds but Site is Blank

• Verify your output_dir matches where your framework outputs built files
• For monorepos, check that root_dir points to the correct directory
• Ensure your build command produces output (check locally first)

Build Takes Too Long

• The build timeout is 10 minutes
• Large node_modules or complex builds may need optimization
• Consider using build caching in your framework configuration