You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that your Exosphere services are running, continue with these guides:
125
+
126
+
-**[Create a Node](./exosphere/register-node.md)** – Learn how to define and register your own node.
127
+
-**[Create a Runtime](./exosphere/create-runtime.md)** – Set up and configure your runtime environment.
128
+
-**[Create a Graph](./exosphere/create-graph.md)** – Build workflows by connecting nodes together.
129
+
-**[Trigger a Graph](./exosphere/trigger-graph.md)** – Execute your workflows and monitor their progress.
130
+
131
+
122
132
## Development Commands
123
133
124
134
=== "Cloud Mongodb"
@@ -257,6 +267,7 @@ You can validate your docker-compose configuration before starting services:
257
267
|`NEXT_PUBLIC_DEFAULT_NAMESPACE`| Default namespace for workflows |`default`|
258
268
259
269
> **🔒 Security Note**: The dashboard now uses **Server-Side Rendering (SSR)** for enhanced security:
270
+
>
260
271
> -**API keys are never exposed** to the browser
261
272
> -**All API calls go through** secure server-side routes
262
273
> -**Production-ready security** architecture
@@ -458,27 +469,6 @@ alias 'docker compose'='docker-compose'
458
469
459
470
4. **SDK connection issues**: Make sure `EXOSPHERE_STATE_MANAGER_URI` points to the correct URL and `EXOSPHERE_API_KEY` matches your `STATE_MANAGER_SECRET`. The `EXOSPHERE_API_KEY` value is checked for equality with the `STATE_MANAGER_SECRET` value when making API requests.
0 commit comments