You need the ezgh CLI, a project, and an image in the project’s
Container Registry whose server listens for HTTP on a port: PORT in its environment,
or 8080.
-
Deploy the image. The service is created, its first revision starts, and ezgh waits until it’s ready, then prints the service with its URL:
ezgh run deploy hello --image <id>.registry.ezghcloud.com/acme/hello:1 -
Call it.
curl https://hello-k3f9a0.run.us-west-1.ezghapps.com/The first request after a quiet period waits while an instance starts.
-
Deploy a new revision. Flags you leave out keep the latest revision’s values:
ezgh run deploy hello --image <id>.registry.ezghcloud.com/acme/hello:2 --max-concurrency 200 --env MODE=prodThe new revision takes all the traffic once it’s ready. Until then, the previous one keeps serving; if it fails, the previous one goes on serving.
-
List its revisions, and split traffic between two of them:
ezgh run revisions hello ezgh run traffic hello latest=90 rrv_k3f9a0x2m7qp=10 -
Delete it. Its URL stops answering, and its revisions and instances are deleted:
ezgh run delete hello --yes
In the console, Run › Create service takes the same settings, and a service’s page has Deploy revision and Actions › Edit traffic.