@output.ai/core 0.1.8-dev.pr156.f70e0a1 → 0.1.8
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 +1 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -191,7 +191,6 @@ The url of the example will receive the payload, plus the workflowId:
|
|
|
191
191
|
To resume the workflow, a POST has to be made with a response payload and the workflowId.
|
|
192
192
|
|
|
193
193
|
- Production: `https://output-api-production.onrender.com/workflow/feedback`
|
|
194
|
-
- Staging: `https://output-api-staging.onrender.com/workflow/feedback`
|
|
195
194
|
- Local: `http://localhost:3001/workflow/feedback`
|
|
196
195
|
|
|
197
196
|
Example:
|
|
@@ -234,7 +233,7 @@ After having the API and the engine running, to start the worker just run:
|
|
|
234
233
|
Necessary env variables to run the worker locally:
|
|
235
234
|
|
|
236
235
|
- `TEMPORAL_ADDRESS`: The temporal backend address, prefer the remote;
|
|
237
|
-
- `TEMPORAL_NAMESPACE`: The name of the namespace, if using remote, use: "output-
|
|
236
|
+
- `TEMPORAL_NAMESPACE`: The name of the namespace, if using remote, use: "output-production.i0jzq";
|
|
238
237
|
- `TEMPORAL_API_KEY`: The API key to access remote temporal. If using local temporal, leave it blank;
|
|
239
238
|
- `CATALOG_ID`: The name of the local catalog, always set this. Use your email;
|
|
240
239
|
- `API_AUTH_KEY`: The API key to access the Framework API. Local can be blank, remote use the proper API Key;
|