@haakco/hostingctl 1.0.407 → 1.0.409
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 +70 -0
- package/bin/platforms.js +0 -6
- package/dist/main.js +30437 -396
- package/dist/main.js.map +1 -1
- package/package.json +9 -6
package/README.md
CHANGED
|
@@ -29,6 +29,37 @@ four siblings, `@haakco/hostingctl-linux-arm64`, `@haakco/hostingctl-darwin-arm6
|
|
|
29
29
|
`@haakco/hostingctl-darwin-x64` and `@haakco/hostingctl-windows-x64`); that package's `bin` **is** the
|
|
30
30
|
native binary, so a machine with no Node installs the platform package directly and needs no runtime.
|
|
31
31
|
|
|
32
|
+
### Which machines it runs on
|
|
33
|
+
|
|
34
|
+
The platform package you install is the one compiled for that machine, and it is built for that
|
|
35
|
+
machine's own baseline rather than a newer one:
|
|
36
|
+
|
|
37
|
+
| Package | Runs on |
|
|
38
|
+
| --- | --- |
|
|
39
|
+
| `hostingctl-linux-x64` | 64-bit x86 Linux with glibc 2.17 or newer — CentOS 7, Debian 8, Ubuntu 16.04 and newer |
|
|
40
|
+
| `hostingctl-linux-arm64` | 64-bit ARM Linux with glibc 2.17 or newer |
|
|
41
|
+
| `hostingctl-windows-x64` | 64-bit Windows, as a native `hostingctl.exe` |
|
|
42
|
+
| `hostingctl-darwin-arm64` | Apple silicon macOS 11 or newer |
|
|
43
|
+
| `hostingctl-darwin-x64` | Intel macOS 10.12 or newer |
|
|
44
|
+
|
|
45
|
+
Those floors come from the toolchain the native payloads are built with: the Linux pair links against glibc
|
|
46
|
+
2.17 through Zig, and the two macOS floors are Rust's deployment targets for those architectures. The macOS
|
|
47
|
+
packages still carry the earlier compiled bundle until the Mac builds their native payloads, so a macOS
|
|
48
|
+
machine older than the floor above may run today's package and is not covered by this statement.
|
|
49
|
+
|
|
50
|
+
### Removing it
|
|
51
|
+
|
|
52
|
+
```bash
|
|
53
|
+
npm uninstall -g @haakco/hostingctl # or the platform package, if that is the one you installed
|
|
54
|
+
rm -rf ~/.config/hostingctl # the stored sessions; Windows: %APPDATA%\hostingctl
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
If `HOSTINGCTL_CONFIG_HOME` or `XDG_CONFIG_HOME` is set, sessions live in that directory instead: remove
|
|
58
|
+
`$HOSTINGCTL_CONFIG_HOME` (or `$XDG_CONFIG_HOME/hostingctl`).
|
|
59
|
+
|
|
60
|
+
The second line is the one that matters: an uninstall leaves the credential file behind, and it is the
|
|
61
|
+
only thing on the machine that can still act as you.
|
|
62
|
+
|
|
32
63
|
`hostingctl update` brings a copy to the published version: it detects how the copy was installed,
|
|
33
64
|
prints the command it will run, runs it, and reads the installed version again to confirm the change.
|
|
34
65
|
`hostingctl update --check` reports the published version and that command without changing anything.
|
|
@@ -170,6 +201,7 @@ metadata and compared against it in CI. The groups, in one line each:
|
|
|
170
201
|
| Command | Covers |
|
|
171
202
|
| --- | --- |
|
|
172
203
|
| `whoami`, `environments`, `system`, `diagnostics` | The session's identity and reach, every environment in a company, what the cluster still holds, and the platform's health answer |
|
|
204
|
+
| `watch` | Those same environment reads as a screen that refreshes itself, for watching a change land |
|
|
173
205
|
| `company` | The company itself, its members and roles, its activity, its logo and favicon, and the invitation journey |
|
|
174
206
|
| `environment` | Create, read, scale, retry; profile coverage, domains and redirects, databases and exports, configuration and secrets, services, site access, shared runtime and application, tools, tuning, retention, portable export, and the release bundle |
|
|
175
207
|
| `application` | Create, rename, remove; build and deploy, build logs, runs and run logs, process schedules; recovery review and confirm; the HTTP cache and path routes; source binding; site access; the WordPress import and URL repair; the administrator credential |
|
|
@@ -194,6 +226,44 @@ Exit status: **0** ok, **1** refused by the API, **2** unusable — bad usage, n
|
|
|
194
226
|
API. A refusal prints the API's message, its actionable `detail` when it sent one, and its `X-Request-Id`,
|
|
195
227
|
which is what joins a failed command to the log line that explains it.
|
|
196
228
|
|
|
229
|
+
## Quick application speed checks
|
|
230
|
+
|
|
231
|
+
```sh
|
|
232
|
+
hostingctl application speed-check <environment-uuid> <application-uuid> --company <slug>
|
|
233
|
+
hostingctl application speed-check <environment-uuid> <application-uuid> --company <slug> --json
|
|
234
|
+
```
|
|
235
|
+
|
|
236
|
+
The API makes three anonymous HEAD requests to the application's generated platform ingress,
|
|
237
|
+
verifies TLS, and reports response-header latency, HTTP/redirect status and cache-header findings.
|
|
238
|
+
The Hosting GUI's **Speed check** task uses the same result. No `--confirm` is needed.
|
|
239
|
+
|
|
240
|
+
This is not a browser audit: no bodies/assets or redirects are fetched, public DNS/CDN paths are
|
|
241
|
+
not measured, and failed timings are null rather than zero. A fast HTTP error is not a fast page.
|
|
242
|
+
The [API contract](../docs/development/api_features.md#on-demand-application-speed-check) owns the
|
|
243
|
+
bounds and interpretation. MacNan owns scheduled, multi-day and deeper monitoring.
|
|
244
|
+
|
|
245
|
+
## Watching a deployment settle
|
|
246
|
+
|
|
247
|
+
`hostingctl watch [uuid…]` draws a read-only screen of every environment in the company, or of just the
|
|
248
|
+
UUIDs you name, and reads again every five seconds. It is part of the Rust build the platform packages
|
|
249
|
+
carry; the JavaScript bundle the parent npm package falls back to does not have it. Each row is what the API
|
|
250
|
+
last observed: the status word, the generation being applied against the generation known ready, whether
|
|
251
|
+
that pair is `live` or `queued`, how old the observation is, and the API's own message.
|
|
252
|
+
|
|
253
|
+
| Key | Does |
|
|
254
|
+
| --- | --- |
|
|
255
|
+
| `↑` `↓` | Move the selection |
|
|
256
|
+
| `enter` | Show or hide the selected environment's detail: both generations named, and the message untruncated |
|
|
257
|
+
| `r` | Read again now instead of waiting out the interval |
|
|
258
|
+
| `c` | Copy a one-line summary of the selected environment |
|
|
259
|
+
| `q`, `Esc`, `Ctrl-C` | Quit and restore the terminal |
|
|
260
|
+
|
|
261
|
+
A read that fails keeps the last successful reading on screen and banners the failure with its bounded
|
|
262
|
+
retry, because a screen that empties itself on a dropped connection takes away the reading you were
|
|
263
|
+
watching exactly when it mattered. Nothing on this screen writes, and it asks the same read as
|
|
264
|
+
`environment show`: `--json` prints that answer as a document for a script, and the command refuses to
|
|
265
|
+
draw into a pipe (exit 2) rather than writing escape codes into it.
|
|
266
|
+
|
|
197
267
|
## Access users
|
|
198
268
|
|
|
199
269
|
Create a native login using an existing public SSH key file, not a private key or a password on argv:
|
package/bin/platforms.js
CHANGED
|
@@ -8,7 +8,6 @@
|
|
|
8
8
|
*
|
|
9
9
|
* `id` is the target's name in this repository and in a release. `platform` and `arch` are Node's own
|
|
10
10
|
* values for the machine the package answers for, and are what npm's `os` and `cpu` fields need.
|
|
11
|
-
* `bunTarget` is the compile target Bun names it by.
|
|
12
11
|
*/
|
|
13
12
|
export const targets = [
|
|
14
13
|
{
|
|
@@ -16,7 +15,6 @@ export const targets = [
|
|
|
16
15
|
package: "@haakco/hostingctl-darwin-arm64",
|
|
17
16
|
platform: "darwin",
|
|
18
17
|
arch: "arm64",
|
|
19
|
-
bunTarget: "bun-darwin-arm64",
|
|
20
18
|
executable: "hostingctl",
|
|
21
19
|
},
|
|
22
20
|
{
|
|
@@ -24,7 +22,6 @@ export const targets = [
|
|
|
24
22
|
package: "@haakco/hostingctl-darwin-x64",
|
|
25
23
|
platform: "darwin",
|
|
26
24
|
arch: "x64",
|
|
27
|
-
bunTarget: "bun-darwin-x64",
|
|
28
25
|
executable: "hostingctl",
|
|
29
26
|
},
|
|
30
27
|
{
|
|
@@ -32,7 +29,6 @@ export const targets = [
|
|
|
32
29
|
package: "@haakco/hostingctl-linux-arm64",
|
|
33
30
|
platform: "linux",
|
|
34
31
|
arch: "arm64",
|
|
35
|
-
bunTarget: "bun-linux-arm64",
|
|
36
32
|
executable: "hostingctl",
|
|
37
33
|
},
|
|
38
34
|
{
|
|
@@ -40,7 +36,6 @@ export const targets = [
|
|
|
40
36
|
package: "@haakco/hostingctl-linux-x64",
|
|
41
37
|
platform: "linux",
|
|
42
38
|
arch: "x64",
|
|
43
|
-
bunTarget: "bun-linux-x64",
|
|
44
39
|
executable: "hostingctl",
|
|
45
40
|
},
|
|
46
41
|
{
|
|
@@ -48,7 +43,6 @@ export const targets = [
|
|
|
48
43
|
package: "@haakco/hostingctl-windows-x64",
|
|
49
44
|
platform: "win32",
|
|
50
45
|
arch: "x64",
|
|
51
|
-
bunTarget: "bun-windows-x64",
|
|
52
46
|
executable: "hostingctl.exe",
|
|
53
47
|
},
|
|
54
48
|
];
|