Persistent Deployments
Keep a model warm behind a stable session UUID
A deployment is a session that stays available between runs. It has a stable session UUID and endpoint.
Create
Choose one model or Pop:
eyepop create deployment --model eyepop.person:latest
eyepop create deployment --pop ./pop.json--model accepts a model alias or UUID. --pop accepts the same forms everywhere: a Pop from eyepop get pops, an ability like eyepop.person:latest, a JSON or YAML file, or an inline body. Add --dashboard to enable the deployment dashboard and open it in your default browser once the deployment is healthy.
The command waits for pipeline_ok, then prints the session UUID to stdout:
UUID=$(eyepop create deployment --model eyepop.person:latest)Inspect and run
eyepop get deployments
eyepop get deployments <session-uuid>
eyepop run --session <session-uuid> --media-path image.jpgrun --session and delete deployment also accept a display name or a UUID prefix of at least 7 characters when it identifies one session. get deployments and patch deployment need the full session UUID.
Update
Patch the deployment in place. Its UUID and endpoint stay the same, but requests may fail while the pipeline restarts.
eyepop patch deployment <session-uuid> --model eyepop.person:latest
eyepop patch deployment <session-uuid> --pop ./pop-v2.jsonThe command waits for the deployment to become ready. Add --no-wait to return after the update is accepted.
Delete
Delete deployments when they are no longer needed. SDK clients attach with the session UUID; see the Python SDK or Node SDK.
Next steps
Run Inference & Evaluations — run against a session you created
Resources — list and delete deployments
Command Reference — every
create deploymentandpatch deploymentflag
Last updated
