Unit commands
Use unit commands for normal deploy work.
dpl check <name>
Section titled “dpl check <name>”Validates one unit.
dpl check django-demoUse it before deploy. It reads the YAML file, checks fields, and resolves references.
dpl deploy <name> [path]
Section titled “dpl deploy <name> [path]”Deploys one unit.
Apps require a .tar.gz archive or stdin:
tar -czf /tmp/app.tar.gz -C app .dpl deploy django-demo /tmp/app.tar.gz
git archive --format=tar.gz HEAD | dpl deploy api -Database units can take an optional SQL dump:
dpl deploy app-dbdpl deploy app-db ./backup.sql.gzOther unit types do not accept a path:
dpl deploy nginxdpl deploy example-domaindpl inspect <name>
Section titled “dpl inspect <name>”Shows deploy state and runtime detail.
dpl inspect django-demoUse it to see:
- active version
- latest deploy status
- failure message
- runtime container status for units that have containers
- timer status for app units
dpl undeploy <name>
Section titled “dpl undeploy <name>”Removes the unit from service.
dpl undeploy django-demoFor app units, this removes the active deployment state and cleans exported files for that version. For runtime units, dpl serve stops supervising the unit and stops its container.
Hidden commands
Section titled “Hidden commands”dpl start <name> and dpl timer <name> <timer> are internal commands. dpl serve calls them.
Run normal deploy and timer work through dpl deploy and the serve daemon.