@haakco/hostingctl 1.0.797 → 1.0.807

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -100,12 +100,18 @@ them.
100
100
  [test users](../docs/development/test_users.md): they exist only in local, `DevelopmentSeeder` creates
101
101
  them, and their password is public development data rather than a credential.
102
102
 
103
- Sign in with the public client's registered ID:
103
+ Sign in:
104
104
 
105
105
  ```text
106
- hostingctl login --api-url https://api.example.com/api/v1 --client-id <client-id>
106
+ hostingctl login
107
107
  ```
108
108
 
109
+ With no flags it signs in to `https://hosting.haak.co/api/v1`. The first-party public client of each known
110
+ installation (production and staging) ships with the CLI, in `cli/src/auth/installations.ts` and
111
+ `crates/hostingctl/src/config.rs`, which a test keeps identical. Any other installation, such as the local
112
+ stack, needs its client: `hostingctl login --api-url http://localhost:8000/api/v1 --client-id <id>`, where the
113
+ id is the API's `PASSPORT_FIRST_PARTY_CLIENT_IDS` (or `HOSTINGCTL_CLIENT_ID`).
114
+
109
115
  The browser completes sign-in and consent. Before the session is written, the API is asked who the new token
110
116
  is (`GET /me`): a token Passport minted but the API will not act on is a failed sign-in, and the working session
111
117
  it would have replaced is left alone.
@@ -123,7 +129,7 @@ rotation on 2026-10-08.
123
129
  One credential file holds several sessions. Each is a profile:
124
130
 
125
131
  ```text
126
- hostingctl login --profile staging --api-url https://api.staging.example.com/api/v1 --client-id <id>
132
+ hostingctl login --profile staging --api-url https://hosting-staging.haakdev.com/api/v1
127
133
  hostingctl whoami --profile staging # or HOSTINGCTL_PROFILE=staging
128
134
  hostingctl auth status # the session a command would use, and its expiry
129
135
  hostingctl auth logout --profile staging # revoke at the API, then remove it here