Files
e2b-dev--e2b/apps/web
Tomas Valenta 5ee371498a fix: clean up middleware rewrite fetch + use next native rewrite response + prefix landing page hostname with www
Simplify fetch

Remove headers

Add rest of headers

Explicitly define fetch options

Remove header manipulation

Test all custom config

Remove out cache header

Remove no cache in header

Remove cache

Tweak fetch options

Remove credentials

Remove referrer

Return to basic setup

Add redirect handling

Stop caching

Remove redirect

Remove no cache

Return old settings

Proxy everything

Modify hostname

Change domain

Change hostname back

Remove caching

Change rewrite mechanism

Add more headers

Remove the rewrite

Follow redirect

Try www

Add log

Try just rewrite

Only pass get requests

Fix error

Change headers passing

Print headers

Test pure rewrite

Remove unused code

Add html replace for ai agents list

Remove logs
2025-03-23 12:20:31 +01:00
..
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-11-26 10:34:04 -08: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-03-21 13:41:27 +01:00
2025-03-21 15:02:41 +00:00
2024-07-17 11:25:55 +02:00
2024-11-26 10:34:04 -08: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

E2B Web App

This repository contains E2D 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.