Mish Ushakov
66ee6df13d
Clarified sandbox data retention policy and error handling. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Clarifies that sandbox data retention is 30 days from creation (not extended by resumes) and specifies NotFound errors when resuming deleted/nonexistent sandboxes. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 8f9706f3f0d90c89dc95c8ede407e86a378e0a97. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Vasek Mlejnsky <vasek@e2b.dev>
E2B Web App
This repository contains E2B Dashboard, documentation, and SDK references.
SDK References
The SDK references are generated from the source code in the packages folder.
Each package has its own SDK reference generator found in {package-dir}/scripts/generate_sdk_ref.sh, it generates markdown files with the following schema: ./src/app/(docs)/docs/sdk-reference/{package-name}/{version}/{module-name}/page.mdx.
When pushed to main, a github workflow checks for diffs in the packages folder, and if any are found, the SDK reference generator is run and the result is auto-commited the incoming branch.
Finally, when building or running the dev server, a prebuild step is run beforehand to generate the SDK reference TOCs and routes in the sdk-reference directory. This can also be run manually using npm run prebuild.
note: sometimes you may see uncommited changes or untracked files in the sdk-reference directory, this is fine and the files can be ignored.