Repository navigation
Proposal: boxd as an optional community sandbox provider #8201
Closed
MichielMAnalytics
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I work on boxd (https://boxd.sh?ref=deer-flow). We run Linux microVMs with a persistent disk, and they
can hibernate and wake again with their processes intact.
I'd like to add
deerflow.community.boxd:BoxdSandboxProvider, an opt-in sandbox provider next toTenki and OpenSandbox. It would mirror the Tenki provider: one isolated machine per user and thread,
the shared warm pool and idle reaper, the full
Sandboxcontract, the SDK as an optionaldeerflow-harness[boxd]extra, unit tests against a fake client and a live test behind thelivemarker. Nothing changes for anyone who doesn't select it.
One question: is an in-tree community provider still the shape you want for a new sandbox backend,
or would you rather see it shipped some other way?
All reactions