Download the PHP package innopanda/laravel-asset-manager without Composer

Laravel Asset Manager

A professional, drop-in asset management package for Laravel, built with Livewire and powered by Spatie Laravel Media Library.

Laravel Asset Manager provides a complete interface for uploading, organizing, browsing, selecting, replacing, versioning, and managing media assets. It can be used independently with Livewire or integrated directly into Filament forms.

✨ Features

• 📁 Virtual Folder Tree Organize assets into nested folders without changing their physical storage paths.

• 🎯 Asset Picker Browse, search, upload, preview, and select assets through a reusable modal interface.

• 🖼️ Thumbnail Generation Generate optimized previews and thumbnails using Spatie Laravel Media Library.

• 📦 Livewire Components Use the asset browser, uploader, folder tree, picker, preview, replacement drawer, and other components independently.

• ☑️ Multiple Asset Selection Select one or multiple assets depending on your application requirements.

• 🔄 File Replacement Replace an existing asset while preserving its previous versions and asset relationships.

• 🕘 Asset Version History Previous versions of replaced files are preserved and can be reviewed or restored.

• 🗑️ Custom Delete Confirmation Assets and folders use styled Livewire confirmation modals instead of native browser JavaScript confirmation dialogs.

• 🏢 Tenant-Aware Architecture Supports optional tenant-based asset isolation.

• 🧩 Filament Integration Use AssetPicker directly inside Filament forms.

• 💾 Spatie Media Library Integration Leverages Spatie Laravel Media Library for media storage, collections, conversions, and file management.

📋 Requirements

• PHP 8.3+
• Laravel 12 or 13
• Livewire 4.x
• Spatie Laravel Media Library 11.x
• Filament 4.x — optional, only required for Filament integration

Filament is an optional dependency. The core Asset Manager and Livewire components can be used without Filament.

📦 Installation

Install the package using Composer:

After installation, Laravel automatically discovers the package service provider.

Verify that the package is installed:

You should see:

Publish Configuration

Publish the Asset Manager configuration file:

This creates:

Publish Database Migrations

Publish the Asset Manager migrations to your application's database/migrations directory:

Then run the migrations:

Verify the migration status:

Publish Frontend Assets

Publish the compiled Asset Manager frontend assets:

The assets will be copied to:

⚙️ Configuration

Publish the configuration file:

This creates:

Example configuration:

Adjust the configuration according to your application's requirements.

🗄️ Database Migrations

The package includes all required database migrations for asset management.

Publish the package migrations to your application's database/migrations directory:

This publishes the Asset Manager migrations, including:

The asset_versions migration is required for File Replacement and Asset Version History functionality.

After publishing the migrations, run:

To verify the migration status:

Note: The package also loads its migrations automatically. Publishing them is recommended when you want the migration files available directly in your Laravel application's database/migrations directory and managed alongside your application's migrations.

Spatie Media Library

Laravel Asset Manager uses Spatie Laravel Media Library for media storage and management.

Make sure the required Spatie migrations are also available in your application.

If required, publish the Spatie Media Library migrations and then run:

The Asset Manager requires the media-related tables to be available before uploading and managing assets.

🖼️ Storage

If you are using the default Laravel public disk, create the storage symlink:

Make sure your .env contains the appropriate disk configuration:

You can use another Laravel filesystem disk if required.

🎨 Publishing Frontend Assets

The package ships its compiled frontend assets.

To publish them:

The assets will be copied to:

Expected files:

If you are developing the package locally, build the package assets from the package repository:

⚡ Livewire Usage

Laravel Asset Manager can be used directly with Livewire without Filament.

Media Browser

Add the Media Browser component to a Blade view:

The browser provides functionality for:

• Folder navigation
• Asset browsing
• Asset searching
• Asset selection
• Asset uploading
• Asset previews

Media Picker

To display the reusable asset picker:

The picker can be used inside your own Livewire forms and components.

Listening for Asset Selection

The asset picker dispatches an asset-selected event.

In the parent Livewire component:

You can then use the selected asset in your application.

🧩 Filament Integration

Filament integration is available when Filament is installed in the host application.

Use the Asset Picker inside a Filament form:

Multiple Selection

To allow multiple assets:

This makes the Asset Manager suitable for:

• Profile images
• Product images
• Gallery images
• Documents
• Other application media

📁 Folder Management

Assets can be organized using virtual folders.

The folder structure does not require changing the physical storage location of the asset.

Example:

Folders can be nested and assets can be moved between folders.

🔄 File Replacement

Existing files can be replaced through the asset management interface.

The replacement functionality is designed to preserve the asset's existing relationships and associations while updating the underlying media.

🧱 Available Livewire Components

The package provides reusable Livewire components including:

These components are registered automatically by the package service provider.

🧪 Testing

The package contains its own PHPUnit test suite.

From the package repository:

Run the complete test suite:

Example:

Run Individual Tests

Run model tests:

Run API tests:

Run Livewire tests:

Run Spatie integration tests:

🎨 Build Frontend Assets

Install Node dependencies:

Build production assets:

The compiled files are generated in:

🔍 Development

Clone the repository:

Enter the package directory:

Install PHP dependencies:

Install frontend dependencies:

Build assets:

Run the test suite:

🏠 Local Package Testing

To test a development version of the package in a Laravel application, you can use a Composer path repository.

In the Laravel application's composer.json:

Then require the package:

Composer will use the local package instead of downloading it from Packagist.

This is recommended when developing and testing the package before creating a release.

🚀 Release Workflow

Before creating a release, run:

Then:

Verify the working tree:

Commit the changes:

Create a version tag:

Push the branch and tag:

🤝 Contributing

Contributions are welcome!

1. Fork the repository.

2. Create a feature branch:

3. Make your changes.
4. Add or update tests.

5. Run the test suite:

6. Build frontend assets:

7. Commit your changes:

8. Push your branch:

9. Open a Pull Request.

Please ensure that existing functionality continues to work and that new functionality includes appropriate tests.

📚 Architecture

The package is structured around several major areas:

The package keeps the asset-management functionality isolated from the host Laravel application.

📜 License

Laravel Asset Manager is open-sourced software licensed under the MIT License.

See the LICENSE file for more information.

🔗 Repository

GitHub:

https://github.com/manojujn05/laravel-media-manager