Umbral Storage

One plugin, two jobs that every app needs and nobody wants to hand-roll: serving your compiled static assets, and storing user uploads. Both go through a single pluggable Storage trait — the local filesystem in dev, S3 in prod, the same handler code either way. Declare an ImageField or FileField on a model and you get multipart upload, streaming size caps, background processing behind a concurrency gate, and an access-control hook so private files aren't world-readable by guessing the URL.

Install

cargo add umbral-storage

Wire it up

use umbral::prelude::*;
use umbral_storage::StoragePlugin;

let app = App::builder()
    .database("default", pool)
    .plugin(
        StoragePlugin::new()
            .static_files("/static", "./static")  // compiled CSS/JS
            .media("/media", "./media"),          // user uploads
    )
    .build()?;

Target: let users upload an avatar

Add the field; the admin and forms render an upload widget with a thumbnail, and the file is stored through whichever backend is configured.

#[derive(Model)]
struct Profile {
    #[umbral(primary_key)]
    id: i64,
    avatar: Option<ImageField>,  // multipart upload, thumbnailed
}

What you get

• One Storage trait: local filesystem in dev, S3 in prod, same code
• FileField / ImageField model fields with upload widgets
• Streaming size caps so a huge upload can't exhaust memory
• Background image processing behind a concurrency gate
• Access-control hook so private uploads aren't public by URL
• Static-asset serving in production (no nginx required to start)