Tomas Valenta

I think there is some problem with your git checked files - building 91e333dafb961a5eeffa769a039bfbbd4c2ae42a was OK for me and I cannot find `components/Editor/Template/NodeJSExpressTemplate/useInstruction` in the whole codebase. Also when you...

> New to using Docker though npm No worries @industriaditat! It is actually `docker compose build` we call in the [npm script command](https://github.com/e2b-dev/e2b/blob/main/package.json#L26) that handles the env vars. The [**error...

If you are running `npm start` for the first time the error should be there but immediately after that the Supabase should be starting. The `;` between the commands should...

That would be great! You can probably try: ``` docker compose build && (npm run db:reset || true && npm run db:start && docker compose up) ``` instead of the...

Great find @voxitme! Can you please try if using `npx [email protected] start` (you may need to stop the db first with `npx supabase stop` first) works on Windows? We may...

@voxitme I pushed an update to `main` with the Supabase version already changed in `package.json` scripts. Can you pull the changes abd do: ``` npm run stop ``` then ```...

Thanks for the PR and sorry for the delay! I just changed some details and now I'm merging it. (The GIF especially was really welcome!)

We are no longer storing keys in local storage. I'm closing this, but thanks again for the report.

This issue is not specific to websockets, but to the management of resource in the sandbox.

This is fixed in the new beta SDK (https://e2b.dev/docs/guide/beta-migration) — by default, all operations are executed as `user`.