@mesh-tech/mesh-cli 0.27.0 → 0.29.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 (19) hide show
  1. package/README.md +11 -2
  2. package/dist/bin/mesh.js +1151 -865
  3. package/dist/bin/mesh.js.map +3 -3
  4. package/dist/build-info.json +2 -2
  5. package/dist/src/commands/app-check-resolve.d.ts +28 -0
  6. package/dist/src/commands/app-check-resolve.js +276 -0
  7. package/dist/src/commands/app-check.d.ts +6 -3
  8. package/dist/src/commands/app-check.js +31 -7
  9. package/dist/src/commands/hub/index.d.ts +2 -0
  10. package/dist/src/commands/hub/index.js +16 -1
  11. package/fragments/base/index.ts.hbs +16 -1
  12. package/package.json +2 -2
  13. package/skills/core/SKILL.md +9 -3
  14. package/templates/api-auth/index.ts.hbs +5 -1
  15. package/templates/api-role-gating/index.ts.hbs +5 -1
  16. package/templates/external-service/index.ts.hbs +5 -1
  17. package/templates/platform-repo/AGENTS.md.hbs +20 -4
  18. package/templates/platform-repo/platform/index.ts +10 -0
  19. package/templates/workflow/index.ts.hbs +5 -1
package/README.md CHANGED
@@ -95,8 +95,17 @@ the deploy sequence — including the one manual step in the middle: **delegatin
95
95
  the NS records** of the new public zone, without which the deploy stalls on its
96
96
  ACM certificate.
97
97
 
98
- The platform layer builds service images with Docker, so it needs a working
99
- Docker daemon; the core layer does not.
98
+ The platform layer builds service images with Docker by default, so it needs a
99
+ working Docker daemon; the core layer does not. On a machine without Docker (a
100
+ cloud IDE container, some CI runners), set `mesh:buildMode: remote` in the
101
+ platform stack config — images then build inside the target cluster as
102
+ rootless-BuildKit Jobs (see `RemoteBuildConfig` in the infra-components apps
103
+ reference). That covers the Temporal namespace provisioner, the custom Temporal
104
+ server, and every Hub workload. Three opt-ins still build on the deploying
105
+ machine and keep a Docker requirement: a Hub with `mesh:hub: { cdn: true }` (its
106
+ CDN asset build runs locally), `mesh:headscale` (the VPN join broker image), and
107
+ `mesh:packageRegistry` (the registry-auth broker image, created unless you pass
108
+ `broker: false`).
100
109
 
101
110
  For an existing app repo, `mesh init app-tenant` is the **doctor**, not a
102
111
  scaffolder: it checks auth, registry access, tenant registration, repo shape and