Add shareable ReadWriteMany volumes across apps

[biersoeckli]

Motivation

• Enable AppVolumes with ReadWriteMany to be shared across multiple apps in the same project so the same PVC can be mounted into foreign apps under independent mount paths.
• Persist sharing metadata on the AppVolume model so deployments and monitoring can reference a single base PVC for shared volumes.

Description

• Add two fields to the AppVolume model in Prisma: shareWithOtherApps (Boolean) and sharedVolumeId (String?) and update the generated Zod model accordingly.
• Extend the client-side volume editor (storage-edit-overlay.tsx) to allow toggling Share with other apps in project for ReadWriteMany volumes and to select an existing shared volume from other apps when adding a volume to a foreign app, preserving an independent mount path per app.
• Add getShareableVolumes server action and getShareableVolumesByProjectId service method to list eligible shared volumes in the same project (must be ReadWriteMany, shareWithOtherApps=true, and not already a shared replica).
• Update saveVolume action to support saving a foreign-app volume that references a sharedVolumeId, including validation that the shared volume belongs to the same project, is from a different app, and is shareable.
• Make PVC handling share-aware in pvc.service.ts so a single base PVC is created for a shared volume and mounted into all apps referencing it, while each app keeps its own mount path; dedupe PVC definitions and map mounts to sharedVolumeId ?? id.
• Adjust monitoring (monitoring.service.ts) and UI list (storages.tsx) to report usage and capacity using the base shared volume when relevant.
• Ensure file browser and restore flows reference the base PVC for shared volumes (file-browser-service.ts, restore.service.ts).

Testing

• Ran the local dev server with yarn dev, the app started and a page screenshot was captured, but full runtime failed at app initialization due to missing Prisma client / NextAuth secret (development environment constraint).
• No unit test changes were added; existing test suite was not executed as part of this rollout due to the dev environment Prisma client issue.
• Manual runtime checks were exercised by launching the dev server and verifying the app compiled and served pages until the Prisma client error occurred.

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
get-quickstack	Ready	Preview, Comment	Jan 30, 2026 8:07am