@envsync-cloud/deploy 0.11.0 → 0.20.2

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 (4) hide show
  1. package/README.md +35 -10
  2. package/dist/cli.js +5237 -0
  3. package/dist/index.js +5062 -167
  4. package/package.json +8 -4
package/README.md CHANGED
@@ -1,15 +1,40 @@
1
- # EnvSync OSS Deploy
1
+ # @envsync-cloud/deploy
2
2
 
3
- Public OSS deploy package.
3
+ **License:** MIT
4
+ **Binary:** `envsync-deploy`
4
5
 
5
- Current responsibilities:
6
+ Public OSS CLI for self-hosted EnvSync on Docker Swarm.
6
7
 
7
- - validate OSS deploy configs against edition rules
8
- - render an OSS topology plan
9
- - omit landing and management API artifacts
10
- - keep observability opt-in
8
+ ## Independence (no piggyback)
11
9
 
12
- Commands:
10
+ This package **owns** the deploy engine (`src/cli.ts` + helpers). It does **not** import
11
+ or spawn `packages/deploy-cli` / `@envsync-cloud/deploy-enterprise`.
13
12
 
14
- - `envsync-deploy validate [deploy.yaml]`
15
- - `envsync-deploy plan [deploy.yaml]`
13
+ | Package | Role |
14
+ |---------|------|
15
+ | `@envsync-cloud/deploy` | OSS engine + `envsync-deploy` bin |
16
+ | `@envsync-cloud/deploy-enterprise` | Thin EE entry: forces `edition=enterprise`, depends on this package |
17
+ | `@envsync-cloud/deploy-core` | Shared plan/schema primitives |
18
+
19
+ ## Install
20
+
21
+ ```bash
22
+ npm i -g @envsync-cloud/deploy
23
+ envsync-deploy --help
24
+ ```
25
+
26
+ Full operator guide (OSS + Enterprise + Hosted): monorepo root [DEPLOY.md](../../DEPLOY.md).
27
+
28
+ ## Enterprise
29
+
30
+ Private package `@envsync-cloud/deploy-enterprise` (`envsync-deploy-enterprise`) wraps
31
+ this engine with enterprise edition forced. Open-core direction: **EE → OSS**, never reverse.
32
+
33
+ Enterprise stacks run a **single API service** with manage routes at `/api/v1/manage/...` on the API host (no separate management-api container). Frontend `managementApiUrl` points at `{apiBaseUrl}/api/v1/manage`.
34
+
35
+ ## Build
36
+
37
+ ```bash
38
+ bun run --filter @envsync-cloud/deploy build
39
+ bun run --filter @envsync-cloud/deploy test
40
+ ```