inngest-cli 1.45.0 → 1.46.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.
- package/README.md +38 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -81,6 +81,44 @@ Open the Inngest Dev Server dashboard at http://localhost:8288:
|
|
|
81
81
|
|
|
82
82
|
Follow our [Next.js](https://www.inngest.com/docs/getting-started/nextjs-quick-start?ref=github-inngest-readme), [Node.js](https://www.inngest.com/docs/getting-started/nodejs-quick-start?ref=github-inngest-readme) or [Python](https://www.inngest.com/docs/getting-started/python-quick-start?ref=github-inngest-readme) quick start guides.
|
|
83
83
|
|
|
84
|
+
### Cloud sandboxes in local development (experimental)
|
|
85
|
+
|
|
86
|
+
With a CLI and JavaScript SDK build that supports Cloud sandboxes, log in once,
|
|
87
|
+
then start the dev server from your project directory:
|
|
88
|
+
|
|
89
|
+
```sh
|
|
90
|
+
inngest login
|
|
91
|
+
inngest dev
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
Select a single existing Cloud development environment during login. That
|
|
95
|
+
environment needs sandbox access and a default VPC; branch-child environments
|
|
96
|
+
without a VPC are not supported. No deployed Cloud app is required. To change
|
|
97
|
+
environments, run `inngest login --force`.
|
|
98
|
+
|
|
99
|
+
Use `inngest.sandboxes` normally, or `step.sandbox` with `sandboxMiddleware`.
|
|
100
|
+
No sandbox token or signing key is needed in your local application. Set
|
|
101
|
+
`INNGEST_DEV` to your dev-server URL if it differs from the default.
|
|
102
|
+
Only sandbox REST requests go to Cloud; functions, events, and runs stay local.
|
|
103
|
+
The dev server uses your saved CLI login and refreshes credentials automatically.
|
|
104
|
+
Cloud credentials remain in the CLI's OS credential store. On headless machines,
|
|
105
|
+
`inngest login --insecure-storage` explicitly opts into private plaintext storage.
|
|
106
|
+
Cloud sandbox routes only accept local connections; use a local port forward
|
|
107
|
+
for remote development.
|
|
108
|
+
|
|
109
|
+
Sandboxes are real, billable Cloud resources. Stopping the dev
|
|
110
|
+
server does **not** destroy them. The Sandboxes page lists resources created
|
|
111
|
+
through this project's bridge and supports pause, resume, and explicit destroy.
|
|
112
|
+
Their IDs are saved under `~/.config/inngest/dev-sandboxes` (or
|
|
113
|
+
`INNGEST_CONFIG_DIR`) independently of `--persist`. Restart from the same project
|
|
114
|
+
directory with the same CLI environment selected to recover the list. Resources
|
|
115
|
+
created elsewhere remain accessible through the SDK or Cloud dashboard.
|
|
116
|
+
|
|
117
|
+
The bridge requires loopback access and the dev server's own UI origin. For a
|
|
118
|
+
remote dev server, use a local port forward; there is no public tunnel or sandbox
|
|
119
|
+
access to your app's localhost. After an ambiguous connection failure, inspect
|
|
120
|
+
the operation's state before repeating a command; the bridge does not retry it.
|
|
121
|
+
|
|
84
122
|
## SDKs
|
|
85
123
|
|
|
86
124
|
- **TypeScript / JavaScript** ([inngest-js](https://github.com/inngest/inngest-js)) - [Reference](https://www.inngest.com/docs/reference/typescript?ref=github-inngest-readme)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "inngest-cli",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.46.0",
|
|
4
4
|
"description": "The leading workflow orchestration platform. Run stateful step functions and AI workflows on serverless, servers, or the edge.",
|
|
5
5
|
"license": "SEE LICENSE IN LICENSE.md",
|
|
6
6
|
"scripts": {
|