You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/volumes.mdx
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ sidebarTitle: Overview
5
5
6
6
Volumes provide persistent storage that exists independently of sandbox lifecycles. Data written to a volume persists even after a sandbox is shut down, and volumes can be mounted to multiple sandboxes over time.
7
7
8
-
### One volume shared across multiple sandboxes
8
+
**One volume shared across multiple sandboxes**
9
9
10
10
```mermaid
11
11
graph LR
@@ -14,14 +14,16 @@ graph LR
14
14
V1 --- S3[Sandbox 3]
15
15
```
16
16
17
-
### Each sandbox with its own volume
17
+
**Each sandbox with its own volume**
18
18
19
19
```mermaid
20
20
graph LR
21
21
V2[Volume A] --- S4[Sandbox 1]
22
22
V3[Volume B] --- S5[Sandbox 2]
23
23
```
24
24
25
+
When a volume is mounted to a sandbox, files can be read and written directly at the mount path. The SDK methods are meant to be used when the volume is not mounted to any sandbox.
26
+
25
27
With E2B SDK you can:
26
28
-[Read and write files to a volume.](/docs/volumes/read-write)
27
29
-[Get file and directory metadata.](/docs/volumes/info)
0 commit comments