App Engine

Use App Engine when a workspace needs many always-on apps, funnels, APIs, or client sites without provisioning a separate production VM for each deployment. The visible product name is App Engine. The CLI and API still use docker_deploy as the internal compatibility value.

Step 1 - Ensure the workspace App Engine host.

miosa api POST /docker-deploy/hosts/ensure -d '{"workspace_id": "<workspace-id>"}'
miosa api GET /docker-deploy/hosts

The host must be active before an App Engine publish can finish.

Step 2 - Publish the sandbox to App Engine.

miosa deploy create --from-sandbox <sandbox-id> 
  --name my-app 
  --dir /workspace 
  --run-command "npm run start" 
  --port 3000 
  --type docker_deploy 
  --wait 
  --wait-timeout 900s 
  --json

The response includes the Deployment and its public_url. That URL may be a MIOSA-managed tenant URL, a workspace deployment domain, a tenant deployment domain, or an exact custom domain. Always show the returned URL.

Step 3 - Confirm the app is live.

miosa deploy get <deployment-id> --json
miosa deploy requests <deployment-id>

deploy get shows the deployment’s status, product and public_url. deploy requests shows the recent HTTP requests served, so you can confirm real traffic reaches the app.

What you just did

StepWhat happened
docker-deploy ensureCreated or returned the workspace App Engine host
sandbox publish --docker-deployPublished the sandbox artifact as a container on that workspace host
docker-deploy doctorProved the container and public URL are real
Was this page helpful?