From 6619d83817b112162aa5c30d2148c62a6d6ff838 Mon Sep 17 00:00:00 2001 From: Edoardo Marangoni <ecmm@anche.no> Date: Mon, 9 Sep 2024 09:25:03 +0200 Subject: [PATCH 1/2] Minor changes to volumes' docs --- pages/edge/learn/volumes.mdx | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/pages/edge/learn/volumes.mdx b/pages/edge/learn/volumes.mdx index e22c34a..5aa1fe7 100644 --- a/pages/edge/learn/volumes.mdx +++ b/pages/edge/learn/volumes.mdx @@ -12,7 +12,7 @@ In the current initial implementation, volumes are restricted to a single [Edge region](/edge/learn/regions). Volumes also at the moment only provide *read-write-many* semantics. -Due the automatic auto-scaling for apps, this means that volumes are not currently +Due to the automatic auto-scaling for apps, this means that volumes are not currently well-suited for databases or other more complex use cases that require a single writer. Keep in mind that volumes can be accessed concurrently, and even from different @@ -22,7 +22,7 @@ These restrictions (including the single-region restriction) will be lifted in the future. </Callout> -## Using Volumes With rclone +## Create and Use Volumes * Every app may have multiple volumes. * Each volume has a name, which must be unique for the application. @@ -39,19 +39,17 @@ volumes: # A name for your volume. # Must be unique for the given app. - name: data - # Where to mount the volume into the filesystem. - # You can specify multiple mounts with optional subpaths. - mounts: - # Mount the volume to `/data`. - - mount_path: /data - # Optional: the subdirectory of the volume to mount. - # subpath: /subpath + # Create a persistent volume named "data" in `/data`. + mount: /data + + - name: more_data + # Create a persistent volume named "more_data" in `/other_mntpoint`. + mount: /other_mntpoint ``` -This will create a new "data" volume, which will be mounted at `/data`. +This will create two new volumes: "data", which will be mounted at `/data` and "more_data" which will be mounted at `/other_mntpoint`. -Now just re-deploy your app with `wasmer deploy`. -The volume will be automatically created. +Now just re-deploy your app with `wasmer deploy`, and the volume will be automatically created. Your application can now use the mount path and treat it as persistent storage. From a707bc95c5f56804eac2b8858b128e107c1c8edb Mon Sep 17 00:00:00 2001 From: Edoardo Marangoni <ecmm@anche.no> Date: Mon, 9 Sep 2024 09:27:38 +0200 Subject: [PATCH 2/2] tabs -> spaces --- pages/edge/learn/volumes.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/edge/learn/volumes.mdx b/pages/edge/learn/volumes.mdx index 5aa1fe7..8a53ac3 100644 --- a/pages/edge/learn/volumes.mdx +++ b/pages/edge/learn/volumes.mdx @@ -40,11 +40,11 @@ volumes: # Must be unique for the given app. - name: data # Create a persistent volume named "data" in `/data`. - mount: /data + mount: /data - name: more_data # Create a persistent volume named "more_data" in `/other_mntpoint`. - mount: /other_mntpoint + mount: /other_mntpoint ``` This will create two new volumes: "data", which will be mounted at `/data` and "more_data" which will be mounted at `/other_mntpoint`.