shared storage (#216)

Author: vankovap

apps/docs/content/references/zsc.mdx

@@ -81,24 +81,35 @@ zsc backup-create db
 
 ---
 
-### connectSharedStorage
+### shared-storage
 
-Connects a shared storage volume to your service for persistent data storage.
+Manages shared storage volumes for persistent data storage.
 
 ```sh
-zsc connectSharedStorage [...name]
+zsc shared-storage [command]
 ```
 
-#### Parameters
-- `name`: Optional name(s) of the shared storage to connect
+#### Available sub-commands
+- `mount`: Mounts the shared storage
+- `unmount`: Unmounts the shared storage
+- `wait`: Waits for readiness of the storage mount
 
 #### Available flags
-- `-h, --help`: Help for the connectSharedStorage command
+- `-h, --help`: Help for the shared-storage command
 
 #### Examples
 ```sh
-zsc connectSharedStorage sharedstorage0
-zsc connectSharedStorage sharedDisk secondDisk
+# View shared-storage help
+zsc shared-storage --help
+
+# Mount a shared storage volume
+zsc shared-storage mount <storage-name>
+
+# Unmount a shared storage volume
+zsc shared-storage unmount <storage-name>
+
+# Wait for a storage mount to be ready
+zsc shared-storage wait <storage-name>
 ```
 
 ---

apps/docs/content/shared-storage/how-to/connect.mdx

@@ -30,6 +30,7 @@ For existing storage, go to the shared storage service detail page and select **
 
 To disconnect storage, access the shared storage service detail page, select **Shared storage connections**, and toggle OFF the desired runtime service.
 
+{/*
 ## Connect using zsc
 
 Connect shared storage from the command line with the `zsc connectSharedStorage` command. Specify one or more storage names as parameters:
@@ -39,4 +40,4 @@ zsc connectSharedStorage sharedstorage0
 zsc connectSharedStorage sharedDisk secondDisk
 ```
 
-Run this command from within your runtime container via web terminal, SSH, or in your `zerops.yml` file. For more details, see the [Zerops Setup Control documentation](/references/zsc).
+Run this command from within your runtime container via web terminal, SSH, or in your `zerops.yml` file. For more details, see the [Zerops Setup Control documentation](/references/zsc).*/}

apps/docs/content/shared-storage/how-to/use.mdx

@@ -25,6 +25,7 @@ If you connect multiple runtimes, the content of the folder will be shared among
 ## Mount Points and Multiple Volumes
 
 - Multiple storage volumes can be mounted to a single service (e.g., `/mnt/files1`, `/mnt/files2`, etc.)
+- Shared storage mount is only available in runtime containers, not during build and prepare runtime phases
 - All filesystem operations are automatically logged to runtime logs
 
 For technical details about mount behavior and filesystem capabilities, see the [Technical Details](/shared-storage/technical-details#mount-integration) page.
@@ -46,4 +47,10 @@ When using Shared Storage, keep in mind:
 - For write-heavy workloads, consider batching operations
 - Minimize operations with many small files for better performance
 
-For more detailed information about performance constraints and limitations, see the [Technical Details](/shared-storage/technical-details#performance-considerations) page.
+For more detailed information about performance constraints and limitations, see the [Technical Details](/shared-storage/technical-details#performance-considerations) page.
+
+## Troubleshooting
+
+### Common Issues
+
+- The `df` command may show incorrect or misleading information when used with shared storage mounts. Please refer to the Zerops GUI for accurate storage metrics.

apps/docs/content/shared-storage/tech-details.mdx

@@ -14,13 +14,16 @@ Shared Storage consists of three main components:
 - **Volume Servers**: Store the actual file data
 - **Filer**: Provides a POSIX-compatible interface for file operations
 
+An **automatic vacuum process** helps maintain optimal storage performance by reclaiming space from deleted files. This process is triggered when the size of deleted content exceeds 15% (reduced from the default 30%).
+
 ### Mount Integration
 
 When connected to a runtime service:
 - Storage is mounted at `/mnt/<storage-hostname>`
 - Mount point is owned by the `zerops` user and group (no sudo required)
 - All filesystem operations are logged to runtime logs (tagged as `zerops-mount-<service-hostname>`)
 - Mounting will overwrite any existing content in the mount directory
+- Shared storage mount is only available in runtime containers, not during build and prepare runtime phases
 
 ## Deployment Modes
 
@@ -90,8 +93,11 @@ Vertical auto scaling has the following default configuration:
 
 <ResourceTable resources={{
   ram: {
-    min: '0.25 GB',
-  }
+    min: '0.5 GB',
+  },
+  disk: {
+      min: '5 GB'
+      }
 }} />
 
 For most cases, the default parameters will work without issues. If you need to limit the cost of the Shared Storage service, lower the maximal resources. Zerops will never scale above the selected maximums.