Deploying

From source to a running endpoint, across dev → uat → prod.

Deploy

The CLI bundles your source, sends the tarball to the registry, builds the container image, and returns an endpoint URL. You never pick infrastructure — gworker selects the backend.

bash
1gworker deploy --env dev

Ignore files

Add a .gworkerignore file to exclude build artifacts, virtual environments, and large files from the upload tarball. Uses gitignore syntax.

bash
1# .gworkerignore2__pycache__/3*.pyc4.venv/5.git/6data/

Environment variables at deploy

Pass env vars directly without creating a secret. For sensitive values, use a named Secret instead.

bash
1gworker deploy --env dev --set-env LOG_LEVEL=debug --set-env WORKERS=4

Stages

Every app has dev, uat, and prod stages. Deploys land in dev; promote forward when ready.

bash
1gworker promote my-app --from dev --to uat2gworker promote my-app --from uat --to prod

Verify

Tail logs while a deploy settles. The endpoint URL is printed after `gworker deploy`.

bash
1gworker logs my-app --env dev --follow