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

doploy_cli-0.2.2/PKG-INFO

@@ -0,0 +1,167 @@
+Metadata-Version: 2.4
+Name: doploy-cli
+Version: 0.2.2
+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.
+
+## Using it from a coding agent
+
+```bash
+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
+
+```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 |
+| `skill install` | Teach Claude Code to use doploy (`skill print` for AGENTS.md) |
+| `logout` | Forget the saved session |
+| `projects` | List your projects |
+| `builds <project>` | Live builds for a project. `--type development\|staging\|production`, `--limit`, `--all` |
+| `branches <project>` | Live branches with their ids |
+| `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.2/README.md

@@ -0,0 +1,145 @@
+# 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.
+
+## Using it from a coding agent
+
+```bash
+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
+
+```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 |
+| `skill install` | Teach Claude Code to use doploy (`skill print` for AGENTS.md) |
+| `logout` | Forget the saved session |
+| `projects` | List your projects |
+| `builds <project>` | Live builds for a project. `--type development\|staging\|production`, `--limit`, `--all` |
+| `branches <project>` | Live branches with their ids |
+| `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.2/doploy_cli/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: doploy
+description: Use the `doploy` CLI to watch Odoo builds, read test failures and logs, and update modules on doploy-hosted deployments. Use when the repo is an Odoo project deployed on doploy, when a build or test run needs checking, or when the user asks to deploy, update modules, or look at logs.
+---
+
+# doploy
+
+`doploy` is the command line for doploy, which builds and hosts Odoo projects from a GitHub
+repo. Every branch push produces a development build with a full Odoo test run. Production and
+staging are long-lived deployments that update in place.
+
+Check it is installed and signed in with `doploy projects`. If that fails, tell the user to run
+`pipx install doploy-cli && doploy login` (it opens a browser; do not try to sign in for them).
+
+## Finding ids
+
+Ids are stable and worth reusing within a session.
+
+```bash
+doploy projects                       # project id (short string, e.g. Bx2Nx)
+doploy builds <project> --type development --limit 5    # build ids, newest first
+doploy branches <project>             # branch ids, for `branch create --from`
+```
+
+Prefer `--json` when you need to parse output.
+
+## The loop after pushing code
+
+1. Push the commit. doploy builds the branch automatically.
+2. `doploy builds <project> --type development --limit 3` until the newest build for your
+   commit leaves `Building`. Poll every 30 seconds or so; builds take several minutes.
+3. On `Error` or `Active Error`: `doploy tests <build> --details` shows every failing test with
+   its traceback. `doploy logs <build> --source test --filter ERROR` shows the surrounding log.
+4. Fix, push, repeat. On `Success`, open the pull request.
+
+Do not create a new build by hand for a branch you already pushed; the push did it.
+
+## Logs
+
+```bash
+doploy logs <build> --source test -f        # follow the test run until the build settles
+doploy logs <build> --source odoo --filter Traceback   # the running container (staging/prod)
+doploy logs <build> --source build           # doploy's own deploy log
+```
+
+## After a merge to staging or production
+
+Code updates land in place. The changed modules still need `odoo-bin -u`:
+
+```bash
+doploy update-modules <build> --wait        # exactly the modules doploy saw change
+```
+
+`--wait` exits non-zero if the update failed; print the tail it shows. Add `--theme` when a
+website theme changed and the user says so.
+
+## Rules
+
+- Anything aimed at production needs `--confirm`. Ask the user before adding it.
+- `doploy backup <build> --confirm --wait` before risky production updates.
+- The CLI cannot delete, restore, or change domains. Do not look for a way around that.
+- Deploy commands may return "Deploy actions are not enabled". The user turns that on in
+  doploy under Settings → Connected apps. Do not retry until they say it is done.

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

@@ -232,7 +232,7 @@ def cmd_login(args):
         _browser_login(base)
     projects = _client(argparse.Namespace(token=None, base=base)).request('GET', '/projects')
     print(f'logged in; {len(projects["projects"])} project(s) visible; config saved to {CONFIG_PATH}')
-    print('Deploy actions: toggle "Allow deploy actions" in Settings > MCP Connections.')
+    print('Deploy actions: toggle "Allow deploy actions" in Settings > Connected apps.')
 
 
 def cmd_logout(args):
@@ -240,7 +240,7 @@ def cmd_logout(args):
     for k in ('token', 'access_token', 'refresh_token', 'client_id', 'expires_at'):
         cfg.pop(k, None)
     _save_config(cfg)
-    print('logged out (revoke the grant in Settings > MCP Connections to kill the session server-side)')
+    print('logged out (revoke the grant in Settings > Connected apps to kill the session server-side)')
 
 
 def cmd_projects(args):
@@ -251,15 +251,39 @@ def cmd_projects(args):
     _table(data['projects'], ['id', 'name', 'odoo_version'])
 
 
+def _short(rows: list[dict]) -> list[dict]:
+    """Table-friendly copies: 7-char commit, minute-precision timestamps."""
+    out = []
+    for r in rows:
+        r = dict(r)
+        if r.get('commit_sha'):
+            r['commit'] = r['commit_sha'][:7]
+        if r.get('created'):
+            r['created'] = r['created'][:16].replace('T', ' ')
+        out.append(r)
+    return out
+
+
 def cmd_builds(args):
     params = {'limit': str(args.limit)}
     if args.type:
         params['type'] = args.type
+    if args.all:
+        params['all'] = '1'
     data = _client(args).request('GET', f'/projects/{args.project}/builds', params=params)
     if args.json:
         print(json.dumps(data, indent=2))
         return
-    _table(data['builds'], ['id', 'type', 'status', 'fqdn', 'commit_sha', 'created'])
+    _table(_short(data['builds']), ['id', 'type', 'status', 'fqdn', 'commit', 'created'])
+
+
+def cmd_branches(args):
+    params = {'all': '1'} if args.all else None
+    data = _client(args).request('GET', f'/projects/{args.project}/branches', params=params)
+    if args.json:
+        print(json.dumps(data, indent=2))
+        return
+    _table(data['branches'], ['id', 'name', 'type'])
 
 
 def cmd_build(args):
@@ -276,9 +300,11 @@ def cmd_tests(args):
     print(f"build {data['build_id']} [{data['build_status']}] — "
           f"{c['error']} errors, {c['fail']} failures, {c['warning']} warnings")
     for r in data['results']:
-        if r['error_type'] == 'WARNING' and not args.warnings:
+        if r['error_type'] not in ('ERROR', 'FAIL') and not args.warnings:
             continue
-        print(f"\n[{r['error_type']}] {r['module']}.{r['test']}")
+        where = (f"{r['module']}.{r['test']}" if r.get('test') and r['test'] != 'Unknown'
+                 else '(module loading)')
+        print(f"\n[{r['error_type']}] {where}")
         if args.details:
             print(r['details'])
 
@@ -329,15 +355,14 @@ def cmd_logs(args):
     if args.source == 'build':
         if data.get('error_summary'):
             print(f"error summary: {data['error_summary']}\n")
-        for t in data.get('tasks') or []:
-            print(f"task {t['id']} [{t['status']}] {t['title']}")
-        if data.get('tasks'):
-            print()
     shown = data['lines']
     for ln in shown:
         print(ln)
     if not args.follow:
-        if data.get('truncated'):
+        if args.filter:
+            print(f"... ({len(shown)} matching line(s) in the last {data.get('total_lines', '?')}; "
+                  f"raise --lines to search further back)", file=sys.stderr)
+        elif data.get('truncated'):
             print(f"... (showing last {len(shown)} lines; use --lines to see more)", file=sys.stderr)
         return
     # Follow: poll and print only what is new. Build and test logs end when
@@ -383,27 +408,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 +439,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):
@@ -442,6 +468,34 @@ def cmd_backup(args):
         sys.exit(1)
 
 
+# --- agent skill ------------------------------------------------------------
+#
+# The skill ships inside the package (doploy_cli/SKILL.md) so no public repo
+# is needed. `doploy skill install` drops it where Claude Code discovers it;
+# `doploy skill print` gives the same text for AGENTS.md / other agents.
+
+def _skill_text() -> str:
+    from importlib import resources
+    return resources.files('doploy_cli').joinpath('SKILL.md').read_text(encoding='utf-8')
+
+
+def _skill_target(project: bool) -> Path:
+    base = Path.cwd() if project else Path.home()
+    return base / '.claude' / 'skills' / 'doploy' / 'SKILL.md'
+
+
+def cmd_skill(args):
+    if args.skill_command == 'print':
+        print(_skill_text(), end='')
+        return
+    target = _skill_target(args.project)
+    target.parent.mkdir(parents=True, exist_ok=True)
+    target.write_text(_skill_text(), encoding='utf-8')
+    scope = 'this project' if args.project else 'all projects'
+    print(f'installed doploy skill for Claude Code ({scope}): {target}')
+    print('Other agents: `doploy skill print >> AGENTS.md`')
+
+
 def main(argv=None):
     p = argparse.ArgumentParser(prog='doploy', description=__doc__.splitlines()[0])
     p.add_argument('--token', help=argparse.SUPPRESS)
@@ -456,17 +510,33 @@ def main(argv=None):
     sp = sub.add_parser('logout', help='forget saved credentials')
     sp.set_defaults(func=cmd_logout)
 
+    sp = sub.add_parser('skill', help='teach coding agents how to use doploy')
+    ssub = sp.add_subparsers(dest='skill_command', required=True)
+    ip = ssub.add_parser('install', help='install the Claude Code skill (~/.claude/skills/doploy)')
+    ip.add_argument('--project', action='store_true',
+                    help='install into ./.claude/skills instead of your home directory')
+    ip.set_defaults(func=cmd_skill)
+    pp = ssub.add_parser('print', help='print the skill text, e.g. for AGENTS.md')
+    pp.set_defaults(func=cmd_skill)
+
     sp = sub.add_parser('projects', help='list your projects')
     sp.add_argument('--json', action='store_true')
     sp.set_defaults(func=cmd_projects)
 
-    sp = sub.add_parser('builds', help='list builds for a project')
+    sp = sub.add_parser('builds', help='list live builds for a project')
     sp.add_argument('project', help='project id (from `doploy projects`)')
     sp.add_argument('--type', choices=['development', 'staging', 'production'])
     sp.add_argument('--limit', type=int, default=20)
+    sp.add_argument('--all', action='store_true', help='include torn-down builds')
     sp.add_argument('--json', action='store_true')
     sp.set_defaults(func=cmd_builds)
 
+    sp = sub.add_parser('branches', help='list live branches for a project')
+    sp.add_argument('project', help='project id (from `doploy projects`)')
+    sp.add_argument('--all', action='store_true', help='include branches whose git ref is gone')
+    sp.add_argument('--json', action='store_true')
+    sp.set_defaults(func=cmd_branches)
+
     sp = sub.add_parser('build', help='show one build')
     sp.add_argument('build_id', type=int)
     sp.set_defaults(func=cmd_build)
@@ -529,12 +599,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.2/doploy_cli.egg-info/PKG-INFO

@@ -0,0 +1,167 @@
+Metadata-Version: 2.4
+Name: doploy-cli
+Version: 0.2.2
+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.
+
+## Using it from a coding agent
+
+```bash
+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
+
+```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 |
+| `skill install` | Teach Claude Code to use doploy (`skill print` for AGENTS.md) |
+| `logout` | Forget the saved session |
+| `projects` | List your projects |
+| `builds <project>` | Live builds for a project. `--type development\|staging\|production`, `--limit`, `--all` |
+| `branches <project>` | Live branches with their ids |
+| `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.2}/doploy_cli.egg-info/SOURCES.txt

@@ -1,6 +1,7 @@
 LICENSE
 README.md
 pyproject.toml
+doploy_cli/SKILL.md
 doploy_cli/__init__.py
 doploy_cli/main.py
 doploy_cli.egg-info/PKG-INFO

{doploy_cli-0.2.0 → doploy_cli-0.2.2}/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.2"
+description = "doploy CLI: watch builds, read logs, and drive Odoo deployments from a terminal"
 readme = "README.md"
 license = { text = "MIT" }
 requires-python = ">=3.10"
@@ -31,3 +31,6 @@ doploy = "doploy_cli.main:main"
 
 [tool.setuptools.packages.find]
 include = ["doploy_cli*"]
+
+[tool.setuptools.package-data]
+doploy_cli = ["SKILL.md"]

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.