@clize/clize 0.10.1 → 0.11.0

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.
Files changed (39) hide show
  1. package/README.md +9 -11
  2. package/dist/cli.js +169 -373
  3. package/dist/cli.js.map +1 -1
  4. package/dist/config.js +1 -12
  5. package/dist/config.js.map +1 -1
  6. package/dist/context.js +32 -50
  7. package/dist/context.js.map +1 -1
  8. package/dist/core/billing.js +21 -17
  9. package/dist/core/billing.js.map +1 -1
  10. package/dist/core/credentials.js +30 -0
  11. package/dist/core/credentials.js.map +1 -0
  12. package/dist/core/domains.js +59 -18
  13. package/dist/core/domains.js.map +1 -1
  14. package/dist/core/setup.js +3 -26
  15. package/dist/core/setup.js.map +1 -1
  16. package/dist/core/sites.js +59 -20
  17. package/dist/core/sites.js.map +1 -1
  18. package/dist/index.js +40 -90
  19. package/dist/index.js.map +1 -1
  20. package/dist/lib/cloudflare.js +4 -0
  21. package/dist/lib/cloudflare.js.map +1 -1
  22. package/dist/lib/crypto.js +57 -0
  23. package/dist/lib/crypto.js.map +1 -0
  24. package/dist/lib/vercel.js +67 -0
  25. package/dist/lib/vercel.js.map +1 -0
  26. package/dist/providers/index.js +15 -3
  27. package/dist/providers/index.js.map +1 -1
  28. package/dist/providers/registrar/cloudflare.js +4 -0
  29. package/dist/providers/registrar/cloudflare.js.map +1 -1
  30. package/dist/providers/registrar/routing.js +91 -0
  31. package/dist/providers/registrar/routing.js.map +1 -0
  32. package/dist/providers/registrar/vercel.js +114 -0
  33. package/dist/providers/registrar/vercel.js.map +1 -0
  34. package/dist/remote.js +13 -8
  35. package/dist/remote.js.map +1 -1
  36. package/dist/state/file-store.js +7 -0
  37. package/dist/state/file-store.js.map +1 -1
  38. package/package.json +1 -1
  39. package/skills/clize-site-debug/SKILL.md +80 -0
package/README.md CHANGED
@@ -33,21 +33,19 @@ clize status # who's waiting, this month's spend
33
33
  clize email inbox acme.clize.app # read what customers sent
34
34
  ```
35
35
 
36
- ## Two ways to run
36
+ ## Hosted — just log in
37
37
 
38
- | Mode | Log in with | What runs where |
39
- |---|---|---|
40
- | **Hosted** (recommended) | `clize login` (GitHub) — or `clize login --api <url> --token clize_…` if you already have a key | Commands call the clize backend; resources run on clize's infra. You never handle Cloudflare. |
41
- | **Self-host** (bring your own Cloudflare) | `clize login --token <CF_API_TOKEN> --account <CF_ACCOUNT_ID>` | Commands run locally against *your* Cloudflare account. |
42
-
43
- Hosted mode covers the full surface — everything in the table below, **including** custom-domain email (`domain import` · `email setup` / `inbox-setup` / `route` / `webhook` / `address`) and `release`.
38
+ | Log in with | What runs where |
39
+ |---|---|
40
+ | `clize login` (web: GitHub / Google / email) — or `clize login --token clize_…` for CI / headless | Commands call the clize backend; resources run on clize's infra. You never touch Cloudflare / Vercel keys. |
44
41
 
45
- Hosted-mode specifics to know before you hit them:
42
+ clize is a **thin client**: the CLI / MCP carry no infrastructure credentials and talk only to the clize control plane — domains, email, deploy, and media all run hosted. (Credentials live in your dashboard; bring-your-own Cloudflare / Vercel is configured there, not on your machine.)
46
43
 
47
- - `clize deploy <dir>` and `clize email send` need `--domain` / `--from` — unless the directory is bound with `clize init --handle <slug>`, which lets both be inferred from `./clize.json` (same as local mode). `--html` single-page deploys are local-only.
48
- - `gen image --ref/--mask` (reference image / mask) and `gen budget` pre-approval are local-only for now — hosted confirms each generation with `--confirm`.
44
+ A few specifics worth knowing:
49
45
 
50
- Self-host needs a Cloudflare API token + Account ID (dashboard → overview, right column). Scope the token to what you'll use: Zone **DNS** + **Email Routing** (email), Account **Workers Scripts** (deploy), Account **Registrar** (domain buy). Run `clize check` to verify connectivity. Free `*.clize.app` handles are allocated by the hosted side — self-host uses your own domains (`clize domain import`).
46
+ - `clize deploy <dir>` and `clize email send` need `--domain` / `--from` — unless the directory is bound with `clize init --handle <slug>`, which infers both from `./clize.json`. Deploy is directory-based (multi-file static sites).
47
+ - `gen image --ref/--mask` (reference image / mask) and `gen budget` pre-approval are coming soon — hosted confirms each generation with `--confirm`.
48
+ - Free `*.clize.app` handle: `clize claim <slug>`. Your own domain: `clize domain buy` / `clize domain import`. Run `clize check` to verify your login.
51
49
 
52
50
  ## What it does
53
51