@haakco/hostingctl 1.0.614 → 1.0.659
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 +30 -1
- package/dist/main.js +3079 -927
- package/dist/main.js.map +1 -1
- package/package.json +1 -1
- package/platform/darwin-arm64/hostingctl +0 -0
- package/platform/darwin-x64/hostingctl +0 -0
- package/platform/linux-arm64/hostingctl +0 -0
- package/platform/linux-x64/hostingctl +0 -0
- package/platform/windows-x64/hostingctl.exe +0 -0
package/README.md
CHANGED
|
@@ -223,6 +223,7 @@ metadata and compared against it in CI. The groups, in one line each:
|
|
|
223
223
|
| `purchases` | What a company was sold: the record, its size and its term |
|
|
224
224
|
| `backup-destination` | The company's own bucket that also receives its backups |
|
|
225
225
|
| `secret-connection` | An environment's connections to a customer's own secret manager |
|
|
226
|
+
| `registry-connections` | A company's container-registry connections: the account, the repository scope, one verified manifest check, credential rotation and revocation. It stores no customer image and starts no workload |
|
|
226
227
|
| `storage` | Purchased object storage: a capacity's price, the purchase, an increase or a resize at that price, which basis the bucket is billed on, the bucket's connection facts, its keys, objects and bindings, the downloads measured for a month, the ceiling that caps the overage bill, and the optional stored-byte maximum that limits growth without buying capacity |
|
|
227
228
|
| `company` | The company itself, its members and roles, its activity, its logo and favicon, and the invitation journey |
|
|
228
229
|
| `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 |
|
|
@@ -268,6 +269,25 @@ not measured, and failed timings are null rather than zero. A fast HTTP error is
|
|
|
268
269
|
The [API contract](../docs/development/api_features.md#on-demand-application-speed-check) owns the
|
|
269
270
|
bounds and interpretation. MacNan owns scheduled, multi-day and deeper monitoring.
|
|
270
271
|
|
|
272
|
+
## One command from a document to a serving environment
|
|
273
|
+
|
|
274
|
+
`environment setup` is the whole journey in one invocation: it creates or adopts the environment, applies your
|
|
275
|
+
`hosting.yaml`, sends each application's source, builds it, deploys the release and follows the environment until
|
|
276
|
+
the platform reports it ready.
|
|
277
|
+
|
|
278
|
+
```sh
|
|
279
|
+
hostingctl environment setup --company acme --name production --file hosting.yaml \
|
|
280
|
+
--source-dir . --confirm
|
|
281
|
+
```
|
|
282
|
+
|
|
283
|
+
`--source-dir` packages the checkout's committed `HEAD` with `git archive` — uncommitted work is not sent, and the
|
|
284
|
+
receipt names the commit it did send. `--source-archive` sends a prepared ZIP instead. Every stage prints on stderr
|
|
285
|
+
with its elapsed time and repeats on a ten-second heartbeat while the platform is still working, so a slow build
|
|
286
|
+
never looks like a stuck command; `--json` keeps stdout to one parseable document. `--dry-run` prints the plan and
|
|
287
|
+
sends nothing, `--confirm` is required to change anything, and a failure keeps the upload, build and release it
|
|
288
|
+
obtained and names the command that reads it. The [client page](https://hosting.haak.co/docs/cli) owns the worked
|
|
289
|
+
example and the reason each step exists.
|
|
290
|
+
|
|
271
291
|
## Watching a deployment settle
|
|
272
292
|
|
|
273
293
|
`hostingctl watch [uuid…]` draws a read-only screen of every environment in the company, or of just the
|
|
@@ -663,6 +683,7 @@ hostingctl environment configuration show <environment-uuid> --company acme
|
|
|
663
683
|
hostingctl environment configuration preview <environment-uuid> --company acme --file acme.yaml
|
|
664
684
|
hostingctl environment configuration save <environment-uuid> --company acme --file acme.yaml --confirm
|
|
665
685
|
hostingctl environment configuration apply <environment-uuid> --company acme --file acme.yaml --confirm
|
|
686
|
+
hostingctl environment configuration apply <environment-uuid> --company acme --file acme.yaml --confirm --wait
|
|
666
687
|
hostingctl environment configuration apply <environment-uuid> --company acme --file acme.yaml \
|
|
667
688
|
--application-uuid <existing-workload-uuid> --confirm
|
|
668
689
|
hostingctl environment secret write <environment-uuid> --company acme \
|
|
@@ -677,7 +698,15 @@ hostingctl environment secret local <environment-uuid> --company acme --out .env
|
|
|
677
698
|
value. `preview` classifies the document and writes nothing; `--apply` reviews it as an apply so the verdict
|
|
678
699
|
is the one an apply relies on. `save` records a **draft** revision (not applied); `apply` records it and queues
|
|
679
700
|
normal reconciliation. Both re-run the review to obtain the hash and generation the API requires, so a
|
|
680
|
-
document that changed since review is refused rather than applied against state nobody saw.
|
|
701
|
+
document that changed since review is refused rather than applied against state nobody saw. `apply --wait`
|
|
702
|
+
then follows the environment until the generation it queued is the one applied, and reports the status word,
|
|
703
|
+
the generation and the platform's own message — the same facts the panel shows. A generation the platform
|
|
704
|
+
reports as failed stops the wait with that message; a dry run sends nothing and waits for nothing.
|
|
705
|
+
|
|
706
|
+
A document may also declare the platform bucket its environment uses (`buckets:` from schema `1.19`), with
|
|
707
|
+
the whole GiB assigned out of the storage the package already includes. The apply founds that bucket, funds
|
|
708
|
+
it and binds it before the applications are created, so the `{storage: …}` references resolve it; the
|
|
709
|
+
reviewed sentence says so before anything is sent.
|
|
681
710
|
For a document with one application, `--application-uuid` explicitly adopts an existing workload in that
|
|
682
711
|
environment. The same UUID is sent in preview and save so the reviewed hash covers the intended adoption.
|
|
683
712
|
|