@mastra/e2b 0.11.0-alpha.3 → 0.11.0-alpha.5

package/README.md

@@ -29,59 +29,15 @@ const agent = new Agent({
 });
 ```
 
-### Timeout Lifecycle
-
-When a sandbox reaches its `timeout`, it is paused by default: the whole VM is snapshotted and the next `start()` reconnects and resumes it. For stateless workspaces whose data lives outside the sandbox (for example mounted from S3), you can have idle sandboxes destroyed instead and recreated on next use:
-
-```typescript
-const sandbox = new E2BSandbox({
-  timeout: 60_000,
-  lifecycle: { onTimeout: 'kill' }, // default: { onTimeout: 'pause' }
-});
-```
-
-Calling `stop()` explicitly always pauses the sandbox, regardless of this setting.
-
-### Mounting Cloud Storage
-
-E2B sandboxes can mount S3, GCS, or Azure Blob filesystems, making cloud storage accessible as a local directory inside the sandbox:
-
-```typescript
-import { Workspace } from '@mastra/core/workspace';
-import { S3Filesystem } from '@mastra/s3';
-import { AzureBlobFilesystem } from '@mastra/azure/blob';
-import { E2BSandbox } from '@mastra/e2b';
-
-const workspace = new Workspace({
-  mounts: {
-    '/data': new S3Filesystem({
-      bucket: 'my-bucket',
-      region: 'us-east-1',
-      accessKeyId: process.env.AWS_ACCESS_KEY_ID,
-      secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
-    }),
-    '/azure-data': new AzureBlobFilesystem({
-      container: 'my-container',
-      connectionString: process.env.AZURE_STORAGE_CONNECTION_STRING,
-      prefix: 'workspace/data',
-    }),
-  },
-  sandbox: new E2BSandbox(),
-});
-```
+## Documentation
 
-### Custom Templates
+- [E2B integration guide](https://mastra.ai/integrations/sandboxes/e2b)
+- [Workspace documentation](https://mastra.ai/docs/mastra-platform/workspaces)
 
-For advanced use cases, you can use custom E2B templates:
+## Changelog
 
-```typescript
-const workspace = new Workspace({
-  sandbox: new E2BSandbox({
-    template: 'my-custom-template',
-  }),
-});
-```
+See the [package changelog](https://github.com/mastra-ai/mastra/blob/main/workspaces/e2b/CHANGELOG.md) for version history and release notes.
 
-## Documentation
+## Support
 
-For more information, see the [Mastra Workspaces documentation](https://mastra.ai/docs/workspace/overview).
+We have an [open community Discord](https://discord.gg/mastra-ai). Come and say hello and let us know if you have any questions or need any help getting things running.

package/dist/index.cjs

@@ -1554,6 +1554,31 @@ var E2BSandbox = class E2BSandbox extends _mastra_core_workspace.MastraSandbox {
 	}
 };
 //#endregion
+//#region ../../packages/_internals/workspace/dist/index.js
+/**
+* Setup completion marker shared by repo templates and their consumers.
+*
+* A repo template writes this file beside the checkout as its last build
+* step, so it exists only in images where every setup command succeeded. Its
+* content is a digest of the setup commands the image ran, letting a sandbox
+* booted from the image tell whether the setup it is about to run already
+* happened. Relative to the template's build cwd, which is also the runtime
+* working directory the repo was cloned into.
+*/
+const SETUP_MARKER_PATH = ".mastra-sandbox/setup";
+/** Blank entries never become build steps, so they never count toward the digest either. */
+function normalizeSetupCommands$1(setupCommand) {
+	return (setupCommand === void 0 ? [] : Array.isArray(setupCommand) ? setupCommand : [setupCommand]).filter((command) => command.trim() !== "");
+}
+/** The marker content for a setup command list: `sha256:<hex>` over the commands joined by newlines. */
+function setupMarkerContent(setupCommand) {
+	return `sha256:${(0, crypto.createHash)("sha256").update(normalizeSetupCommands$1(setupCommand).join("\n")).digest("hex")}`;
+}
+/** Shell step that writes the marker relative to the cwd. `content` is a digest, so it is shell-safe. */
+function setupMarkerCommand(content) {
+	return `mkdir -p "$(dirname "${SETUP_MARKER_PATH}")" && printf '%s' '${content}' > "${SETUP_MARKER_PATH}"`;
+}
+//#endregion
 //#region src/utils/repo-template.ts
 /**
 * Sha-tagged repo templates.
@@ -1773,7 +1798,9 @@ function buildRepoTemplateSpec(identity, token) {
 	}
 	template = template.runCmd(`git ${auth}clone ${cloneUrl} "${repoDir}"`);
 	if (sha) template = template.runCmd(`git -C "${repoDir}" ${auth}fetch origin ${sha}`).runCmd(`git -C "${repoDir}" checkout ${sha}`);
-	for (const command of normalizeSetupCommands(setupCommand)) template = template.runCmd(`cd "${repoDir}" && ${command}`);
+	const setupCommands = normalizeSetupCommands(setupCommand);
+	for (const command of setupCommands) template = template.runCmd(`cd "${repoDir}" && ${command}`);
+	template = template.runCmd(setupMarkerCommand(setupMarkerContent(setupCommands)));
 	return {
 		ref: repoTemplateRef(identity),
 		template,