20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
# Add local Docker deployment
|
|
|
|
## Why
|
|
|
|
Operators need a repeatable way to run the platform backend, run worker, and platform web console with persistent local data. Local debugging also needs clear environment files so storage paths, run identity, platform API proxying, and browser-facing API URLs are easy to modify without changing code.
|
|
|
|
## What Changes
|
|
|
|
- Add Dockerfiles for `platform/`, `run/`, and `platform_web/`.
|
|
- Add a root `docker-compose.yml` that starts platform, run worker, and web console with named volumes for platform data and run workspace/spool data.
|
|
- Add local `.env.example` files documenting the runtime variables for Docker and direct local execution.
|
|
- Update README files to explain Docker deployment, local direct execution, and which config files to edit.
|
|
|
|
## Impact
|
|
|
|
- Adds local deployment configuration only; it does not add billing, cloud host sales, external provider workflows, or production log database adapters.
|
|
- Keeps platform data durable through mounted volumes and the existing file storage backend.
|
|
- Keeps frontend/browser access platform-mediated through `/api/v1` proxying.
|
|
|