How thesouldev/goboxd works
goboxd is documented as an HTTP service that compiles and runs untrusted code in isolated sandboxes and returns results, optionally checking supplied test cases. The README also describes a YAML-driven language registry, queued bounded concurrency, per-request limits, and liveness/readiness probes. The supplied tree contains no implementation files beyond placeholders, so component paths use the documented entry-point directory or the enclosing internal directory; relationships not established by the README are omitted or marked unverified.
Main entry points: goboxd HTTP service · internal Isolated sandbox
Components 11
HTTP service
- HTTP service
cmd/goboxd - Execution result
cmd/goboxd
Code execution
- Language registry
internal - Compile and run
internal - Optional test cases
internal
Isolation and limits
- Isolated sandbox
internal - Namespaces and cgroups
internal - Request limits
internal
Service operations
- Bounded concurrency
internal - Liveness and readiness
internal
Other components
- HTTP caller
Connections 10
- HTTP caller → HTTP service: submits code
README.md - HTTP service → Isolated sandbox: executes within
README.md - HTTP service → Execution result: returns result
README.md - HTTP service → Language registry: uses languages
- HTTP service → Compile and run: compiles and runs
README.md - HTTP service → Optional test cases: checks optionally
README.md - Isolated sandbox → Namespaces and cgroups: isolated by
README.md - HTTP service → Request limits: applies per request
- HTTP service → Bounded concurrency: queues requests
- HTTP service → Liveness and readiness: exposes