MyWebDrive Guide

Your guide to identity, files, uploads, sharing, publications and Core-first operations in MyWebDrive.

What these guides cover

MyWebDrive is a file storage and distribution service. Core handles identity, file metadata, upload intents, quota, shares and publications. Storage transfers objects and processes background jobs. The Next.js interface talks to the public API through same-origin Nginx. The former separate Auth, User, Metadata, Sharing and Gateway control plane is soft-retired — its startup and migration instructions don't describe the active stack.

These guides were checked against public main, the public OpenAPI contract, components and tests on 2026-09-07. The source project uses the MIT license. Historical sensitive-material remediation remains unresolved, so this site publishes reviewed usage instructions while withholding source acquisition and repository Issue links. This is not a security clearance for the repository. If you hold a maintainer-reviewed copy, you can follow Local development.

Choose your workflow

Goal	Read
Sign in and upload your first file	Quick start, Sign-in and sessions
Inspect files, versions and downloads	Files and versions
Understand progress, retries and space	Uploads, Quota
Distribute to recipients or the public	Sharing, Publications
Administer users, metrics and notifications	Users, Dashboard, Notifications
Integrate or operate an instance	API, Local development, Deployment
Recover from a failed operation	Troubleshooting

Instance routes and actual capabilities

These paths belong to your MyWebDrive instance, not this documentation site: /signin for authentication, /account for personal files, /download for the public catalogue, /admin/overview for the dashboard, /admin/users for users, /admin/publish for publications, and /admin/notifications for notifications.

Not every implemented API has a corresponding button. The account page lets you upload, list files, inspect versions and download. It doesn't offer general rename, move, delete, recycle-bin restore or folder creation. Share management and replacement uploads require API integration. A version list doesn't imply a restore action. Old screenshots or folder fields don't establish that an operation is available.

Verification boundary

Feature descriptions are based on the pinned source. Documentation, search and AI tests are recorded separately from runtime acceptance of a MyWebDrive instance. A reachable homepage doesn't prove real email delivery, upload finalization or download integrity. Follow Quick start with a small, non-sensitive file to verify an actual round trip.