rendez-cli 0.1.0__tar.gz → 0.1.1__tar.gz

{rendez_cli-0.1.0/rendez_cli.egg-info → rendez_cli-0.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rendez-cli
-Version: 0.1.0
+Version: 0.1.1
 Summary: Put your repository into a Rendez session, from your terminal
 License-Expression: MIT
 Project-URL: Homepage, https://rendez.space
@@ -27,18 +27,33 @@ This puts the *files* somewhere useful — the repository already checked out on
 your machine, instead of an empty directory on the server.
 
 ```bash
-pipx install "git+https://github.com/rendez-engine/hive.git#subdirectory=cli"
+pipx install rendez-cli
 
 cd ~/code/your-repo
 rendez connect -g "add rate limiting"
 ```
 
-Not on PyPI: the name `rendez` there belongs to an unrelated project, so the
-distribution would be `rendez-cli` (the installed command stays `rendez`).
-Authentication works and the server is deployed; what is still open before
-publishing is a protocol-version handshake, so an installed CLI and a
-redeployed server cannot drift apart silently (`DEPLOYMENT.md` §10).
-Installing from the repository needs read access to it.
+**On PyPI as `rendez-cli`**; the installed command is `rendez`. The names
+differ because `rendez` on PyPI belongs to an unrelated project -- a
+distribution and its entry point need not match.
+
+It defaults to the deployed service (`rendez.space`). Point it somewhere else
+with `--api`/`--web`, or `RENDEZ_API`/`RENDEZ_WEB`, which is what a local
+stack needs.
+
+The client sends a wire-protocol version and reads the server's on `/health`
+(`DEC-092`). An installed CLI that has fallen behind a redeployed server says
+so and names the upgrade, rather than failing somewhere less legible:
+
+```bash
+pipx upgrade rendez-cli
+```
+
+Installing from the repository still works for people with access to it:
+
+```bash
+pipx install "git+https://github.com/rendez-engine/hive.git#subdirectory=cli"
+```
 
 **HTTPS rather than `git+ssh`**, which assumes a GitHub SSH key that a
 developer may not have — `gh auth login` covers HTTPS and is already how most

{rendez_cli-0.1.0 → rendez_cli-0.1.1}/README.md

@@ -8,18 +8,33 @@ This puts the *files* somewhere useful — the repository already checked out on
 your machine, instead of an empty directory on the server.
 
 ```bash
-pipx install "git+https://github.com/rendez-engine/hive.git#subdirectory=cli"
+pipx install rendez-cli
 
 cd ~/code/your-repo
 rendez connect -g "add rate limiting"
 ```
 
-Not on PyPI: the name `rendez` there belongs to an unrelated project, so the
-distribution would be `rendez-cli` (the installed command stays `rendez`).
-Authentication works and the server is deployed; what is still open before
-publishing is a protocol-version handshake, so an installed CLI and a
-redeployed server cannot drift apart silently (`DEPLOYMENT.md` §10).
-Installing from the repository needs read access to it.
+**On PyPI as `rendez-cli`**; the installed command is `rendez`. The names
+differ because `rendez` on PyPI belongs to an unrelated project -- a
+distribution and its entry point need not match.
+
+It defaults to the deployed service (`rendez.space`). Point it somewhere else
+with `--api`/`--web`, or `RENDEZ_API`/`RENDEZ_WEB`, which is what a local
+stack needs.
+
+The client sends a wire-protocol version and reads the server's on `/health`
+(`DEC-092`). An installed CLI that has fallen behind a redeployed server says
+so and names the upgrade, rather than failing somewhere less legible:
+
+```bash
+pipx upgrade rendez-cli
+```
+
+Installing from the repository still works for people with access to it:
+
+```bash
+pipx install "git+https://github.com/rendez-engine/hive.git#subdirectory=cli"
+```
 
 **HTTPS rather than `git+ssh`**, which assumes a GitHub SSH key that a
 developer may not have — `gh auth login` covers HTTPS and is already how most

{rendez_cli-0.1.0 → rendez_cli-0.1.1}/pyproject.toml

@@ -16,7 +16,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "rendez-cli"
-version = "0.1.0"
+version = "0.1.1"
 description = "Put your repository into a Rendez session, from your terminal"
 readme = "README.md"
 license = "MIT"

{rendez_cli-0.1.0 → rendez_cli-0.1.1}/rendez/__init__.py

@@ -887,6 +887,20 @@ async def run(args: argparse.Namespace) -> int:
     except urllib.error.URLError as exc:
         print(f"Authentication check failed: {exc}", file=sys.stderr)
         return 1
+    # The browser will not let you start a session without a provider key
+    # (`DEC-052`), and the server does not enforce it either way -- so this
+    # client used to create a session that could never answer, which is a
+    # worse dead end than the refusal (`DEC-094`, `R-103`). Best-effort: a
+    # server too old for the route, or one that errors, must not block a
+    # session over a check that is only advisory.
+    try:
+        if not (api_json(f"{api}/account/keys", token) or {}).get("keys"):
+            print("No API key on this account, so a session could not answer.\n"
+                  f"Add one at {args.web.rstrip('/')}/sessions, then run this again.",
+                  file=sys.stderr)
+            return 1
+    except Exception:                                    # noqa: BLE001
+        pass
     try:
         sid = args.session
         # Before the stdin reader exists: `choose_session` reads the fd

{rendez_cli-0.1.0 → rendez_cli-0.1.1/rendez_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rendez-cli
-Version: 0.1.0
+Version: 0.1.1
 Summary: Put your repository into a Rendez session, from your terminal
 License-Expression: MIT
 Project-URL: Homepage, https://rendez.space
@@ -27,18 +27,33 @@ This puts the *files* somewhere useful — the repository already checked out on
 your machine, instead of an empty directory on the server.
 
 ```bash
-pipx install "git+https://github.com/rendez-engine/hive.git#subdirectory=cli"
+pipx install rendez-cli
 
 cd ~/code/your-repo
 rendez connect -g "add rate limiting"
 ```
 
-Not on PyPI: the name `rendez` there belongs to an unrelated project, so the
-distribution would be `rendez-cli` (the installed command stays `rendez`).
-Authentication works and the server is deployed; what is still open before
-publishing is a protocol-version handshake, so an installed CLI and a
-redeployed server cannot drift apart silently (`DEPLOYMENT.md` §10).
-Installing from the repository needs read access to it.
+**On PyPI as `rendez-cli`**; the installed command is `rendez`. The names
+differ because `rendez` on PyPI belongs to an unrelated project -- a
+distribution and its entry point need not match.
+
+It defaults to the deployed service (`rendez.space`). Point it somewhere else
+with `--api`/`--web`, or `RENDEZ_API`/`RENDEZ_WEB`, which is what a local
+stack needs.
+
+The client sends a wire-protocol version and reads the server's on `/health`
+(`DEC-092`). An installed CLI that has fallen behind a redeployed server says
+so and names the upgrade, rather than failing somewhere less legible:
+
+```bash
+pipx upgrade rendez-cli
+```
+
+Installing from the repository still works for people with access to it:
+
+```bash
+pipx install "git+https://github.com/rendez-engine/hive.git#subdirectory=cli"
+```
 
 **HTTPS rather than `git+ssh`**, which assumes a GitHub SSH key that a
 developer may not have — `gh auth login` covers HTTPS and is already how most