doploy CLI

The command line for doploy, the Odoo hosting and CI platform. Watch builds, read test results and logs, and drive deployments from your terminal.

$ doploy builds acme --type development
ID    TYPE         STATUS        FQDN                        COMMIT_SHA  CREATED
418   development  Active Error  doploy-k3j9x2.doploy.site   9f1c2ab     2026-09-11T14:02:11

$ doploy tests 418
build 418 [Active Error] — 1 errors, 0 failures, 2 warnings

[ERROR] sale_custom.test_discounts

Install

pipx install doploy-cli

or with pip, uv, or pip install --user:

pip install doploy-cli
uv tool install doploy-cli

Requires Python 3.10 or newer.

Using it from a coding agent

doploy skill install

Installs a skill file so Claude Code knows when to use doploy, how to find ids, and the push → build → read failures → fix loop. doploy skill print >> AGENTS.md does the same for Codex and other agents.

Sign in

doploy login

Your browser opens, you sign in with your doploy account, and the CLI is connected. Sessions renew themselves. Sign out with doploy logout.

What the CLI may do is decided per app in Settings → Connected apps on the doploy dashboard: read only, or read and deploy, on all projects or only some. Change it there at any time; the change applies on the CLI's next command.

Quick start

doploy projects                              # your projects and their ids
doploy builds <project-id> --type staging    # recent builds
doploy build <build-id>                      # one build in full
doploy tests <build-id> --details            # test failures with tracebacks
doploy logs <build-id> --source test -f      # follow the test log until the build settles

Commands

Commands that print tables accept --json for machine-readable output.

Anything aimed at a production deployment requires --confirm. Nothing destructive is available: no deletes, no restores, no domain changes.

Examples

Why did my build fail?

doploy builds acme --type development --limit 1
doploy tests 418 --details
doploy logs 418 --source test --filter ERROR

Follow a build as it runs

doploy logs 419 --source test -f

Exits on its own when the build settles. --source odoo follows the running container's log instead and runs until Ctrl-C.

Ship a change to staging

doploy update-modules 302 --wait

Updates exactly the modules doploy saw change in the last code update, waits for Odoo to finish, and exits non-zero if the update failed. Add --theme to rebuild website theme assets, or leave it out and doploy decides from the module list.

Take a backup first

doploy backup 301 --confirm --wait --comment "before v2.4"

Log sources

Links

• Documentation: https://docs.doploy.io/agents/cli
• Dashboard: https://cloud.doploy.io
• Support: support@doploy.io

License

MIT