@aopslabs/aops 0.3.1 → 0.3.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 (8) hide show
  1. package/README.md +11 -12
  2. package/THIRD_PARTY_NOTICES +16169 -0
  3. package/dist/commands/community-server.js +5 -2
  4. package/dist/lib/community-diagnostic.js +1 -1
  5. package/dist/lib/community-native-lifecycle.js +70 -7
  6. package/dist/lib/setup-readiness.js +2 -2
  7. package/native/tui/win32-x64/aops-tui.exe +0 -0
  8. package/package.json +3 -2
package/README.md CHANGED
@@ -1,8 +1,8 @@
1
1
  # @aopslabs/aops
2
2
 
3
- AOPS CLI and terminal setup application. It can connect to a remote AOPS Server
4
- without installing a local Server, or manage a separately installed local
5
- Server.
3
+ AOPS CLI and terminal setup application. The package brings the exact compatible
4
+ local Server runtime, but remote-only users can use the CLI without configuring
5
+ or starting that local Server.
6
6
 
7
7
  ```sh
8
8
  npm install --global @aopslabs/aops
@@ -16,11 +16,9 @@ aops cockpit
16
16
  aops assets
17
17
  ```
18
18
 
19
- For a local installation, install the Server package separately:
20
-
21
- ```sh
22
- npm install --global @aopslabs/aops @aopslabs/aops-server
23
- ```
19
+ That one command also installs the exact compatible `@aopslabs/aops-server`
20
+ runtime. npm installation itself never starts services or runs migrations;
21
+ `aops setup init` is the explicit first-time setup boundary.
24
22
 
25
23
  The source repositories remain private. Customer-required runtime dependencies
26
24
  may also be published as public npm packages so ordinary installation never
@@ -166,10 +164,11 @@ Eligible DDL runs transactionally under a non-waiting migration lock and the
166
164
  live semantic schema is read back before success. Optional audit-write failure
167
165
  does not invalidate that result.
168
166
 
169
- The CLI package does not force-install `@aopslabs/aops-server`. Remote users need
170
- only the CLI; local users install the matching Server package separately. No
171
- customer path requires Git or a source checkout. Advanced developers can still
172
- run an explicit checkout with `--source-root`.
167
+ The CLI package depends exactly on the compatible `@aopslabs/aops-server`
168
+ release, so local installation remains a single npm command. Remote users may
169
+ leave that local runtime unconfigured and connect only to their selected remote
170
+ target. No customer path requires Git or a source checkout. Advanced developers
171
+ can still run an explicit checkout with `--source-root`.
173
172
  A stopped installation can move between valid checkout/npm roots through the
174
173
  same setup command without reset or duplicate rollback copies; same-root npm
175
174
  byte drift still requires reinstalling the package.