@nebulr-group/bridge-cli 0.4.2 → 0.4.3
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 +31 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -66,6 +66,37 @@ export BRIDGE_TENANT_ID=<tenant-id> # for user commands
|
|
|
66
66
|
export BRIDGE_DEBUG=true # enable debug logging
|
|
67
67
|
```
|
|
68
68
|
|
|
69
|
+
### 3. Targeting a local stack
|
|
70
|
+
|
|
71
|
+
Two exports, then log in as usual — the browser flow works against a local
|
|
72
|
+
stack the same way it does against production:
|
|
73
|
+
|
|
74
|
+
```bash
|
|
75
|
+
export BRIDGE_BASE_URL=http://localhost:3200 # bridge-api
|
|
76
|
+
export BRIDGE_AUTH_BASE_URL=http://localhost:3091 # consent screen (cloud-views)
|
|
77
|
+
|
|
78
|
+
bridge auth login
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
`BRIDGE_BASE_URL` is where commands send their API calls; `BRIDGE_AUTH_BASE_URL`
|
|
82
|
+
is where `bridge auth login` opens the consent screen. Set the second one too,
|
|
83
|
+
or you will authenticate against production and then issue commands against
|
|
84
|
+
your local API with a token it does not accept.
|
|
85
|
+
|
|
86
|
+
There is deliberately **no config file to source** (TBP-121). A sourceable file
|
|
87
|
+
mixed CLI settings with two demo apps' settings, pinned an undocumented app id,
|
|
88
|
+
and kept a long-lived API key on disk in plaintext; two exports cover the same
|
|
89
|
+
ground without any of that. For CI, use `BRIDGE_API_KEY` as described above.
|
|
90
|
+
|
|
91
|
+
One more, for working on the integration guides themselves:
|
|
92
|
+
|
|
93
|
+
```bash
|
|
94
|
+
export BRIDGE_GUIDE_LOCAL_DIR=/path/to/thebridge-platform/bridge-plugins
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
`bridge guide` and `bridge integrate` then read prompts from that directory
|
|
98
|
+
instead of fetching them from GitHub, so edits show up without a release.
|
|
99
|
+
|
|
69
100
|
## Usage
|
|
70
101
|
|
|
71
102
|
All output is JSON by default for management commands. AI agents parse it directly; humans can pipe through `jq`. The `bridge auth status` and `bridge auth login` commands print human-readable text, since their primary audience is a human in a terminal.
|