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
Copy file name to clipboardExpand all lines: docs/how-it-works/gateways/container-deployment.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,7 +156,7 @@ the repository contains a production-ready Compose setup with full inline docume
156
156
157
157
| File | Purpose |
158
158
|---|---|
159
-
|`docker-compose.yml`| Gateway service, volumes, and environment variables |
159
+
|`docker-compose.yml`| Gateway and init services, volumes, and environment variables |
160
160
|`gateway.toml`| TOML configuration mounted into the container |
161
161
162
162
Clone or copy those files, then start the gateway:
@@ -165,6 +165,8 @@ Clone or copy those files, then start the gateway:
165
165
docker compose -f deploy/docker/docker-compose.yml up -d
166
166
```
167
167
168
+
The `init` service runs first and writes the sandbox JWT signing keys to `/var/lib/openshell/tls` on the host. The Docker driver requires them, and existing keys are kept. Do not commit them. This setup disables TLS and user authentication and publishes the port on loopback only.
169
+
168
170
Register the gateway with the CLI. If registering from the same machine:
0 commit comments