UMedia brings configured storage providers into one self-hosted web interface (Docker Compose + SQLite). Early beta: local filesystem and S3-compatible storage are marked available; Google Drive, OneDrive, Dropbox, and Telegram are beta. Verification varies by operation. Default compose.yaml expects existing Traefik routing; README also has a local Caddy sample (compose.release.yaml). umedia.uln.me is the public landing page; hosted app is a maintainer preview, with no public signup.

I’m building UMedia to bring files from configured storage providers into one self-hosted library. I’d love feedback on the setup experience and which provider operations you would like me to verify next. Please report technical issues on GitHub: https://github.com/mahdikiani/um...

Hi, I m Mahdi, UMedia s maintainer. I m building an MIT-licensed, self-hosted media library that brings files from configured storage providers into one web interface. It runs with Docker Compose and SQLite.

The public landing page is https://umedia.uln.me/. The hosted instance is a maintainer preview with no public signup. Local filesystem and S3-compatible storage are marked available; Google Drive, OneDrive, Dropbox, and Telegram are beta. Provider operations have different verification levels.

I m using this early beta to learn where self-hosters need more confidence. Which provider and operation would be most useful for me to verify next? Which step in the setup guide needs the most clarification?

For technical issues, GitHub Issues is the support route: https://github.com/mahdikiani/um...

UMedia

Self-hosted media library across configured storage

Self-hosted media library across configured storage

Forum Threads

Which provider operations should I verify next in UMedia?

Forum Threads

Which provider operations should I verify next in UMedia?