Deploy an app

Build from a specific Git revision and run the application independently of your development workspace.

Deployment requirements

The node needs the configured Docker Engine socket, Docker CLI and Buildx, and the daemon must be authorized to use them. Your project needs a Git source containing the desired revision and build recipe.

Build and run a revision

Resolve the branch to its full Git object ID before creating a deployment. Replace the example repository and project ID:

readylab project create demo --repo https://example.org/demo.git --branch main
PROJECT_ID='<project-uuid>'
REVISION="$(git ls-remote https://example.org/demo.git refs/heads/main | cut -f1)"
readylab --wait deployment create "$PROJECT_ID" web \
  --revision "$REVISION" --context . --dockerfile Dockerfile \
  --cpu-millis 1000 --memory-mb 512

The revision must exist in the remote. --wait follows the durable build/deploy operation until it finishes. The deployment captures the exact source revision, recipe and resources.

Inspect and manage the app

readylab deployment list "$PROJECT_ID"
readylab deployment logs <deployment-uuid> --tail 100
readylab --wait deployment restart <deployment-uuid>
readylab --wait deployment stop <deployment-uuid>
readylab --wait deployment start <deployment-uuid>

These operations affect the app deployment. They do not start or stop the development workspace. Both environments still depend on the node staying powered on.

Keep app data deliberately

Use explicitly managed volumes for persistent app data. Deleting a deployment retains its managed volumes; volume deletion is a separate operation. Check active references before removing retained data.