DI and actions

The facade is the recommended default, not the only way in. Three entry points run the same code: the MediaLibrary facade (shortest), the manager RoundlyConsulting\MediaLibrary\MediaLibraryManager — the facade's root, a container singleton also aliased media — injected through the constructor (same API, explicit dependency, no static calls), and actions (single-purpose classes with execute(), for composing into your own actions, jobs and commands).

Inject the manager

use RoundlyConsulting\MediaLibrary\MediaLibraryManager;

final class AvatarController
{
    public function __construct(private MediaLibraryManager $media) {}

    public function store(Request $request): Media
    {
        return $this->media->for($request->user())->addFromRequest('avatar')->toBucket('avatar');
    }
}

Call an action

use RoundlyConsulting\MediaLibrary\Actions\MoveMediaAction;
use RoundlyConsulting\MediaLibrary\Actions\RegenerateVariantsAction;

app(MoveMediaAction::class)->execute($media, $otherUser, 'gallery', 'cold');
app(RegenerateVariantsAction::class)->execute($media, only: ['thumb'], force: true);

Facade method → action

• Every mutation — from the facade, a for() handle, the trait or a Media model method — funnels through one manager verb that resolves one action from the container, so a container override of an action applies everywhere.
• MediaLibrary::fake() swaps the manager in the container too, so injected managers are faked as well. Calling an action directly bypasses the fake.
• GenerateVariantsAction is an internal building block (it renders exactly the definitions it is handed) — regenerate through RegenerateVariantsAction or MediaLibrary::regenerate().