Files
e2b-dev--e2b/apps/web
Jiri Sveceny c0a41722e5 Secured sandbox auto signature (#845)
Some users report that JS/Python types lack a `useSignature` attribute,
which only works when `secure=true` is set for the sandbox. This change
removes the `useSignatrue` parameter and makes all upload/download URL
requests signed if `secure` was provided, making sure the function will
work for all possible cases.

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Ben Fornefeld <50748440+ben-fornefeld@users.noreply.github.com>
2025-08-04 12:34:59 +00:00
..
2025-08-04 12:34:59 +00:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2025-07-03 12:59:32 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-10-14 12:22:42 -07:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-10-15 11:51:53 -07:00
2025-04-01 13:44:27 +02:00

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.