Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

build: rename server runtime binaries

Browse Source
This commit is contained in:
Hare
2026-07-29 19:36:05 +09:00
parent 699290ccb1
commit fb285b17e4
16 changed files with 90 additions and 84 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/design/workspace-runtime-docker.md
+3 -3
View File
@@ -32,10 +32,10 @@ Current image roles:
```text
yoi-runtime:latest
worker-runtime-rest-server
yoi-runtime
yoi-server:latest
yoi-workspace-server
yoi-server
yoi-webui:latest
nginx serving built WebUI assets and proxying API requests
@@ -62,7 +62,7 @@ docker/workspace/.yoi/workspace.toml
docker/workspace/.yoi/workspace-backend.local.toml
```
The WebUI container serves static assets and proxies `/api` to the Backend Server. The Backend Server registers the Runtime container as a remote Runtime such as `docker-runtime`. The Runtime container runs `worker-runtime-rest-server` and owns Worker spawning/materialization for that runtime.
The WebUI container serves static assets and proxies `/api` to the Backend Server. The Backend Server registers the Runtime container as a remote Runtime such as `docker-runtime`. The Runtime container runs `yoi-runtime` and owns Worker spawning/materialization for that runtime.
Container user and writable data directories matter: runtime/server images must be able to write their configured data directories and named volumes. The current local-image Compose setup avoids an image-level `User` override and sets data-directory permissions accordingly.