doploy-cli 0.2.0__tar.gz → 0.2.1__tar.gz

doploy_cli-0.2.1/PKG-INFO

@@ -0,0 +1,155 @@
+Metadata-Version: 2.4
+Name: doploy-cli
+Version: 0.2.1
+Summary: doploy CLI: watch builds, read logs, and drive Odoo deployments from a terminal
+License: MIT
+Project-URL: Homepage, https://doploy.io
+Project-URL: Documentation, https://docs.doploy.io
+Project-URL: Dashboard, https://cloud.doploy.io
+Keywords: doploy,odoo,deploy,ci,cli
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx>=0.27
+Dynamic: license-file
+
+# doploy CLI
+
+[![PyPI](https://img.shields.io/pypi/v/doploy-cli.svg)](https://pypi.org/project/doploy-cli/)
+[![Python](https://img.shields.io/pypi/pyversions/doploy-cli.svg)](https://pypi.org/project/doploy-cli/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
+
+The command line for [doploy](https://doploy.io), the Odoo hosting and CI platform.
+Watch builds, read test results and logs, and drive deployments from your terminal.
+
+```console
+$ 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
+
+```bash
+pipx install doploy-cli
+```
+
+or with `pip`, `uv`, or `pip install --user`:
+
+```bash
+pip install doploy-cli
+uv tool install doploy-cli
+```
+
+Requires Python 3.10 or newer.
+
+## Sign in
+
+```bash
+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
+
+```bash
+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
+
+| Command | Description |
+|---|---|
+| `login` | Sign in with your browser |
+| `logout` | Forget the saved session |
+| `projects` | List your projects |
+| `builds <project>` | Recent builds for a project. `--type development\|staging\|production`, `--limit` |
+| `build <id>` | One build: status, commit, versions, error summary |
+| `tests <build>` | Test failures for a build. `--details` prints tracebacks, `--warnings` includes warnings |
+| `logs <build>` | Tail logs. `--source build\|test\|odoo`, `--lines`, `--filter TEXT`, `-f` to follow |
+| `branch create <project> <name>` | Fork a development branch on GitHub and queue its build. `--from <branch-id>` |
+| `rebuild <build>` | Queue a rebuild of a deployment |
+| `restart <build>` | Restart the Odoo service |
+| `update-modules <build> [modules]` | Run `odoo-bin -u` on the modules doploy detected as changed, or the ones you list. `--theme`, `--no-theme`, `--wait` |
+| `operation <id>` | Check a queued module update. `--wait` |
+| `backup <build>` | Take a database and filestore backup. `--comment`, `--wait` |
+
+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?**
+
+```bash
+doploy builds acme --type development --limit 1
+doploy tests 418 --details
+doploy logs 418 --source test --filter ERROR
+```
+
+**Follow a build as it runs**
+
+```bash
+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**
+
+```bash
+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**
+
+```bash
+doploy backup 301 --confirm --wait --comment "before v2.4"
+```
+
+## Log sources
+
+| `--source` | What you get |
+|---|---|
+| `build` | doploy's own build log and error summary. Fast, default. |
+| `test` | The Odoo test run output of a development build. What actually failed. |
+| `odoo` | The running Odoo container's log. Runtime tracebacks on staging and production. |
+
+## Links
+
+- Documentation: https://docs.doploy.io/agents/cli
+- Dashboard: https://cloud.doploy.io
+- Support: support@doploy.io
+
+## License
+
+MIT

doploy_cli-0.2.1/README.md

@@ -0,0 +1,133 @@
+# doploy CLI
+
+[![PyPI](https://img.shields.io/pypi/v/doploy-cli.svg)](https://pypi.org/project/doploy-cli/)
+[![Python](https://img.shields.io/pypi/pyversions/doploy-cli.svg)](https://pypi.org/project/doploy-cli/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
+
+The command line for [doploy](https://doploy.io), the Odoo hosting and CI platform.
+Watch builds, read test results and logs, and drive deployments from your terminal.
+
+```console
+$ 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
+
+```bash
+pipx install doploy-cli
+```
+
+or with `pip`, `uv`, or `pip install --user`:
+
+```bash
+pip install doploy-cli
+uv tool install doploy-cli
+```
+
+Requires Python 3.10 or newer.
+
+## Sign in
+
+```bash
+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
+
+```bash
+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
+
+| Command | Description |
+|---|---|
+| `login` | Sign in with your browser |
+| `logout` | Forget the saved session |
+| `projects` | List your projects |
+| `builds <project>` | Recent builds for a project. `--type development\|staging\|production`, `--limit` |
+| `build <id>` | One build: status, commit, versions, error summary |
+| `tests <build>` | Test failures for a build. `--details` prints tracebacks, `--warnings` includes warnings |
+| `logs <build>` | Tail logs. `--source build\|test\|odoo`, `--lines`, `--filter TEXT`, `-f` to follow |
+| `branch create <project> <name>` | Fork a development branch on GitHub and queue its build. `--from <branch-id>` |
+| `rebuild <build>` | Queue a rebuild of a deployment |
+| `restart <build>` | Restart the Odoo service |
+| `update-modules <build> [modules]` | Run `odoo-bin -u` on the modules doploy detected as changed, or the ones you list. `--theme`, `--no-theme`, `--wait` |
+| `operation <id>` | Check a queued module update. `--wait` |
+| `backup <build>` | Take a database and filestore backup. `--comment`, `--wait` |
+
+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?**
+
+```bash
+doploy builds acme --type development --limit 1
+doploy tests 418 --details
+doploy logs 418 --source test --filter ERROR
+```
+
+**Follow a build as it runs**
+
+```bash
+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**
+
+```bash
+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**
+
+```bash
+doploy backup 301 --confirm --wait --comment "before v2.4"
+```
+
+## Log sources
+
+| `--source` | What you get |
+|---|---|
+| `build` | doploy's own build log and error summary. Fast, default. |
+| `test` | The Odoo test run output of a development build. What actually failed. |
+| `odoo` | The running Odoo container's log. Runtime tracebacks on staging and production. |
+
+## Links
+
+- Documentation: https://docs.doploy.io/agents/cli
+- Dashboard: https://cloud.doploy.io
+- Support: support@doploy.io
+
+## License
+
+MIT

{doploy_cli-0.2.0 → doploy_cli-0.2.1}/doploy_cli/main.py

@@ -383,27 +383,28 @@ def cmd_update_modules(args):
         body['install_theme'] = args.theme
     data = _client(args).request('POST', f'/builds/{args.build_id}/update-modules', json=body)
     theme = ' with INSTALL_THEME=1' if data.get('install_theme') else ''
-    print(f"update queued (task {data['task_id']}): {', '.join(data['modules'])}{theme}")
+    print(f"update queued (operation {data['operation_id']}): {', '.join(data['modules'])}{theme}")
     if not args.wait:
-        print(f"poll with: doploy task {data['task_id']}")
+        print(f"check with: doploy operation {data['operation_id']}")
         return
-    task = _wait_for_task(_client(args), data['task_id'], args.interval)
-    _print_task(task)
-    if task['status'] != 'completed' or (task.get('result') or {}).get('ok') is False:
+    op = _wait_for_operation(_client(args), data['operation_id'], args.interval)
+    _print_operation(op)
+    if op['status'] != 'completed' or (op.get('result') or {}).get('ok') is False:
         sys.exit(1)
 
 
-def _wait_for_task(client: Client, task_id: int, interval: float) -> dict:
+def _wait_for_operation(client: Client, operation_id: int, interval: float) -> dict:
     while True:
-        task = client.request('GET', f'/tasks/{task_id}')['task']
-        if task['status'] in ('completed', 'failed', 'cancelled'):
-            return task
+        op = client.request('GET', f'/operations/{operation_id}')['operation']
+        if op['status'] in ('completed', 'failed', 'cancelled'):
+            return op
         time.sleep(interval)
 
 
-def _print_task(task: dict) -> None:
-    print(f"task {task['id']} [{task['status']}] {task['title']}")
-    result = task.get('result')
+def _print_operation(op: dict) -> None:
+    what = f"update modules {', '.join(op['modules'])}" if op.get('modules') else op.get('kind') or 'operation'
+    print(f"operation {op['id']} [{op['status']}] {what}")
+    result = op.get('result')
     if result:
         if 'exit_code' in result:
             print(f"exit code: {result['exit_code']}")
@@ -413,14 +414,14 @@ def _print_task(task: dict) -> None:
             print(result['output'])
 
 
-def cmd_task(args):
+def cmd_operation(args):
     client = _client(args)
-    task = _wait_for_task(client, args.task_id, args.interval) if args.wait \
-        else client.request('GET', f'/tasks/{args.task_id}')['task']
+    op = _wait_for_operation(client, args.operation_id, args.interval) if args.wait \
+        else client.request('GET', f'/operations/{args.operation_id}')['operation']
     if args.json:
-        print(json.dumps(task, indent=2))
+        print(json.dumps(op, indent=2))
         return
-    _print_task(task)
+    _print_operation(op)
 
 
 def cmd_backup(args):
@@ -529,12 +530,12 @@ def main(argv=None):
     sp.add_argument('--interval', type=float, default=10.0, help='poll seconds for --wait')
     sp.set_defaults(func=cmd_update_modules)
 
-    sp = sub.add_parser('task', help='show a queued task (module update)')
-    sp.add_argument('task_id', type=int)
+    sp = sub.add_parser('operation', help='check a queued module update')
+    sp.add_argument('operation_id', type=int)
     sp.add_argument('--wait', action='store_true', help='block until it finishes')
     sp.add_argument('--interval', type=float, default=10.0)
     sp.add_argument('--json', action='store_true')
-    sp.set_defaults(func=cmd_task)
+    sp.set_defaults(func=cmd_operation)
 
     sp = sub.add_parser('backup', help='start a backup of a deployment (deploy scope)')
     sp.add_argument('build_id', type=int)

doploy_cli-0.2.1/doploy_cli.egg-info/PKG-INFO

@@ -0,0 +1,155 @@
+Metadata-Version: 2.4
+Name: doploy-cli
+Version: 0.2.1
+Summary: doploy CLI: watch builds, read logs, and drive Odoo deployments from a terminal
+License: MIT
+Project-URL: Homepage, https://doploy.io
+Project-URL: Documentation, https://docs.doploy.io
+Project-URL: Dashboard, https://cloud.doploy.io
+Keywords: doploy,odoo,deploy,ci,cli
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx>=0.27
+Dynamic: license-file
+
+# doploy CLI
+
+[![PyPI](https://img.shields.io/pypi/v/doploy-cli.svg)](https://pypi.org/project/doploy-cli/)
+[![Python](https://img.shields.io/pypi/pyversions/doploy-cli.svg)](https://pypi.org/project/doploy-cli/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
+
+The command line for [doploy](https://doploy.io), the Odoo hosting and CI platform.
+Watch builds, read test results and logs, and drive deployments from your terminal.
+
+```console
+$ 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
+
+```bash
+pipx install doploy-cli
+```
+
+or with `pip`, `uv`, or `pip install --user`:
+
+```bash
+pip install doploy-cli
+uv tool install doploy-cli
+```
+
+Requires Python 3.10 or newer.
+
+## Sign in
+
+```bash
+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
+
+```bash
+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
+
+| Command | Description |
+|---|---|
+| `login` | Sign in with your browser |
+| `logout` | Forget the saved session |
+| `projects` | List your projects |
+| `builds <project>` | Recent builds for a project. `--type development\|staging\|production`, `--limit` |
+| `build <id>` | One build: status, commit, versions, error summary |
+| `tests <build>` | Test failures for a build. `--details` prints tracebacks, `--warnings` includes warnings |
+| `logs <build>` | Tail logs. `--source build\|test\|odoo`, `--lines`, `--filter TEXT`, `-f` to follow |
+| `branch create <project> <name>` | Fork a development branch on GitHub and queue its build. `--from <branch-id>` |
+| `rebuild <build>` | Queue a rebuild of a deployment |
+| `restart <build>` | Restart the Odoo service |
+| `update-modules <build> [modules]` | Run `odoo-bin -u` on the modules doploy detected as changed, or the ones you list. `--theme`, `--no-theme`, `--wait` |
+| `operation <id>` | Check a queued module update. `--wait` |
+| `backup <build>` | Take a database and filestore backup. `--comment`, `--wait` |
+
+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?**
+
+```bash
+doploy builds acme --type development --limit 1
+doploy tests 418 --details
+doploy logs 418 --source test --filter ERROR
+```
+
+**Follow a build as it runs**
+
+```bash
+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**
+
+```bash
+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**
+
+```bash
+doploy backup 301 --confirm --wait --comment "before v2.4"
+```
+
+## Log sources
+
+| `--source` | What you get |
+|---|---|
+| `build` | doploy's own build log and error summary. Fast, default. |
+| `test` | The Odoo test run output of a development build. What actually failed. |
+| `odoo` | The running Odoo container's log. Runtime tracebacks on staging and production. |
+
+## Links
+
+- Documentation: https://docs.doploy.io/agents/cli
+- Dashboard: https://cloud.doploy.io
+- Support: support@doploy.io
+
+## License
+
+MIT

{doploy_cli-0.2.0 → doploy_cli-0.2.1}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "doploy-cli"
-version = "0.2.0"
-description = "doploy CLI: watch builds, read logs, and drive Odoo deployments from a terminal or CI"
+version = "0.2.1"
+description = "doploy CLI: watch builds, read logs, and drive Odoo deployments from a terminal"
 readme = "README.md"
 license = { text = "MIT" }
 requires-python = ">=3.10"

doploy_cli-0.2.0/PKG-INFO

@@ -1,63 +0,0 @@
-Metadata-Version: 2.4
-Name: doploy-cli
-Version: 0.2.0
-Summary: doploy CLI: watch builds, read logs, and drive Odoo deployments from a terminal or CI
-License: MIT
-Project-URL: Homepage, https://doploy.io
-Project-URL: Documentation, https://docs.doploy.io
-Project-URL: Dashboard, https://cloud.doploy.io
-Keywords: doploy,odoo,deploy,ci,cli
-Classifier: Development Status :: 4 - Beta
-Classifier: Environment :: Console
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Topic :: Software Development :: Build Tools
-Requires-Python: >=3.10
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: httpx>=0.27
-Dynamic: license-file
-
-# doploy CLI
-
-Watch builds, read logs, and drive your Odoo deployments on [doploy](https://doploy.io)
-from a terminal or a CI pipeline.
-
-```bash
-pipx install doploy-cli
-doploy login          # opens your browser; no tokens to paste
-doploy projects
-doploy builds <project-id> --type production
-doploy logs <build-id> --source test -f
-doploy update-modules <build-id> --wait
-```
-
-## Auth
-
-`doploy login` signs you in with your doploy account (OAuth, PKCE, loopback
-callback). Tokens refresh themselves and live in `~/.config/doploy/config.json`
-(mode 0600). Whether the CLI may deploy is controlled per app in
-Settings > Connected apps.
-
-
-## Commands
-
-| Command | What it does |
-|---|---|
-| `projects` | List your projects |
-| `builds <project>` | Recent builds, filter with `--type` |
-| `build <id>` | One build in full |
-| `tests <build>` | Test failures, `--details` for tracebacks |
-| `logs <build>` | Tail logs; `--source build\|test\|odoo`, `-f` to follow |
-| `branch create <project> <name>` | Fork a dev branch and queue its build |
-| `rebuild <build>` | Queue a rebuild |
-| `restart <build>` | Restart the Odoo service |
-| `update-modules <build> [modules]` | Run `odoo-bin -u`; `--theme`, `--wait` |
-| `backup <build>` | Start a backup; `--wait` |
-| `task <id>` | Poll a queued task |
-| `logout` | Forget saved credentials |
-
-Production targets always need `--confirm`. Destructive operations
-(deletes, restores) are not exposed.

doploy_cli-0.2.0/README.md

@@ -1,41 +0,0 @@
-# doploy CLI
-
-Watch builds, read logs, and drive your Odoo deployments on [doploy](https://doploy.io)
-from a terminal or a CI pipeline.
-
-```bash
-pipx install doploy-cli
-doploy login          # opens your browser; no tokens to paste
-doploy projects
-doploy builds <project-id> --type production
-doploy logs <build-id> --source test -f
-doploy update-modules <build-id> --wait
-```
-
-## Auth
-
-`doploy login` signs you in with your doploy account (OAuth, PKCE, loopback
-callback). Tokens refresh themselves and live in `~/.config/doploy/config.json`
-(mode 0600). Whether the CLI may deploy is controlled per app in
-Settings > Connected apps.
-
-
-## Commands
-
-| Command | What it does |
-|---|---|
-| `projects` | List your projects |
-| `builds <project>` | Recent builds, filter with `--type` |
-| `build <id>` | One build in full |
-| `tests <build>` | Test failures, `--details` for tracebacks |
-| `logs <build>` | Tail logs; `--source build\|test\|odoo`, `-f` to follow |
-| `branch create <project> <name>` | Fork a dev branch and queue its build |
-| `rebuild <build>` | Queue a rebuild |
-| `restart <build>` | Restart the Odoo service |
-| `update-modules <build> [modules]` | Run `odoo-bin -u`; `--theme`, `--wait` |
-| `backup <build>` | Start a backup; `--wait` |
-| `task <id>` | Poll a queued task |
-| `logout` | Forget saved credentials |
-
-Production targets always need `--confirm`. Destructive operations
-(deletes, restores) are not exposed.

doploy_cli-0.2.0/doploy_cli.egg-info/PKG-INFO

@@ -1,63 +0,0 @@
-Metadata-Version: 2.4
-Name: doploy-cli
-Version: 0.2.0
-Summary: doploy CLI: watch builds, read logs, and drive Odoo deployments from a terminal or CI
-License: MIT
-Project-URL: Homepage, https://doploy.io
-Project-URL: Documentation, https://docs.doploy.io
-Project-URL: Dashboard, https://cloud.doploy.io
-Keywords: doploy,odoo,deploy,ci,cli
-Classifier: Development Status :: 4 - Beta
-Classifier: Environment :: Console
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Topic :: Software Development :: Build Tools
-Requires-Python: >=3.10
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: httpx>=0.27
-Dynamic: license-file
-
-# doploy CLI
-
-Watch builds, read logs, and drive your Odoo deployments on [doploy](https://doploy.io)
-from a terminal or a CI pipeline.
-
-```bash
-pipx install doploy-cli
-doploy login          # opens your browser; no tokens to paste
-doploy projects
-doploy builds <project-id> --type production
-doploy logs <build-id> --source test -f
-doploy update-modules <build-id> --wait
-```
-
-## Auth
-
-`doploy login` signs you in with your doploy account (OAuth, PKCE, loopback
-callback). Tokens refresh themselves and live in `~/.config/doploy/config.json`
-(mode 0600). Whether the CLI may deploy is controlled per app in
-Settings > Connected apps.
-
-
-## Commands
-
-| Command | What it does |
-|---|---|
-| `projects` | List your projects |
-| `builds <project>` | Recent builds, filter with `--type` |
-| `build <id>` | One build in full |
-| `tests <build>` | Test failures, `--details` for tracebacks |
-| `logs <build>` | Tail logs; `--source build\|test\|odoo`, `-f` to follow |
-| `branch create <project> <name>` | Fork a dev branch and queue its build |
-| `rebuild <build>` | Queue a rebuild |
-| `restart <build>` | Restart the Odoo service |
-| `update-modules <build> [modules]` | Run `odoo-bin -u`; `--theme`, `--wait` |
-| `backup <build>` | Start a backup; `--wait` |
-| `task <id>` | Poll a queued task |
-| `logout` | Forget saved credentials |
-
-Production targets always need `--confirm`. Destructive operations
-(deletes, restores) are not exposed.