Directories
¶
| Path | Synopsis |
|---|---|
|
Package agent defines the pluggable contract for whatever speaks the envd wire protocol inside a sandbox.
|
Package agent defines the pluggable contract for whatever speaks the envd wire protocol inside a sandbox. |
|
upstream
Package upstream is the Phase 1 AgentProvider.
|
Package upstream is the Phase 1 AgentProvider. |
|
Package api holds the HTTP-facing glue for edvabe: dispatch router, reverse proxy, and (later) the control-plane handlers.
|
Package api holds the HTTP-facing glue for edvabe: dispatch router, reverse proxy, and (later) the control-plane handlers. |
|
dashboard
Package dashboard serves an embedded HTML overview of running sandboxes and templates.
|
Package dashboard serves an embedded HTML overview of running sandboxes and templates. |
|
Package dns implements a minimal UDP DNS server that answers A queries for <port>-<id>.<domain> hostnames with a configured IPv4 address.
|
Package dns implements a minimal UDP DNS server that answers A queries for <port>-<id>.<domain> hostnames with a configured IPv4 address. |
|
Package doctor runs a preflight check over the environment edvabe needs to `serve` and prints an aligned pass/fail table.
|
Package doctor runs a preflight check over the environment edvabe needs to `serve` and prints an aligned pass/fail table. |
|
Package runtime defines the pluggable sandbox runtime contract.
|
Package runtime defines the pluggable sandbox runtime contract. |
|
docker
Package docker is the Phase 1 Runtime implementation backed by a local Docker daemon via github.com/docker/docker/client.
|
Package docker is the Phase 1 Runtime implementation backed by a local Docker daemon via github.com/docker/docker/client. |
|
noop
Package noop is an in-memory Runtime used by unit tests of higher layers (sandbox manager, control plane).
|
Package noop is an in-memory Runtime used by unit tests of higher layers (sandbox manager, control plane). |
|
Package sandbox owns the in-memory registry of active sandboxes and drives their lifecycle: minting IDs and tokens, delegating container creation to the runtime, handshaking with the in-sandbox agent, and reaping sandboxes whose TTL has lapsed.
|
Package sandbox owns the in-memory registry of active sandboxes and drives their lifecycle: minting IDs and tokens, delegating container creation to the runtime, handshaking with the in-sandbox agent, and reaping sandboxes whose TTL has lapsed. |
|
Package template owns the persistent metadata store for user-defined sandbox templates and the types shared between the control plane, the builder runtime, and the sandbox manager.
|
Package template owns the persistent metadata store for user-defined sandbox templates and the types shared between the control plane, the builder runtime, and the sandbox manager. |
|
builder
Package builder owns the async template build runtime — translator from SDK step arrays into generated Dockerfiles, file-context staging, and the BuildManager state machine that drives docker build to completion.
|
Package builder owns the async template build runtime — translator from SDK step arrays into generated Dockerfiles, file-context staging, and the BuildManager state machine that drives docker build to completion. |
|
filecache
Package filecache is the content-addressed blob store edvabe uses for template file contexts.
|
Package filecache is the content-addressed blob store edvabe uses for template file contexts. |
Click to show internal directories.
Click to hide internal directories.