nurbekjummayev/laravel-media-api
Composer 安装命令:
composer require nurbekjummayev/laravel-media-api
包简介
Standalone media/file upload API for Laravel — upload once, get an id, link it from each model's own table. Private storage with token access and orphan cleanup.
README 文档
README
Standalone media/file upload API for Laravel. Upload once, get an id, then each model links it from its own table. Private storage with temporary signed-URL access and automatic orphan cleanup. Built with spatie/laravel-package-tools.
Requirements
- PHP
^8.3 - Laravel 12 or 13
Install
composer require nurbekjummayev/laravel-media-api php artisan migrate
Installing as a local path package
If you keep the package in your app's packages/ directory, add it to the root composer.json:
"repositories": [ { "type": "path", "url": "packages/nurbekjummayev/laravel-media-api" } ], "require": { "nurbekjummayev/laravel-media-api": "*" }
composer update nurbekjummayev/laravel-media-api php artisan migrate
Files are stored under media/private and media/public (project root). Publish config if needed:
php artisan vendor:publish --tag="laravel-media-api-config"
API
| Method | URI | Auth |
|---|---|---|
POST |
/api/v1/media |
auth:api + can:media.upload |
GET |
/api/v1/media/{uuid}/view |
temporary signed URL |
GET |
/api/v1/media/{uuid}/download |
temporary signed URL |
DELETE |
/api/v1/media/{id} |
auth:api + can:media.delete |
Upload accepts files[] (+ optional type=public|private) and returns Media[] with id, uuid, and a temporary signed url. Newly uploaded media are attached=false.
Uploads are atomic — the whole request runs in a DB transaction. If any file fails to write to disk or its Media record can't be saved, the transaction rolls back and every file already written for that request is removed, so no orphan files are left behind.
view/download are protected by Laravel temporary signed URLs (validated against APP_KEY, expire after config('media.url_ttl')). Read the signed view URL from $media->url and the download URL from $media->downloadUrl() — never hand-build these URLs. Inline view responses also send X-Content-Type-Options: nosniff and a sandbox CSP so SVG/HTML files can't execute scripts.
Linking media — each model owns its link
There is no shared polymorphic pivot. A model that needs media defines its own table/column.
Many files — a dedicated per-model table (e.g. product_photos):
// migration Schema::create('product_photos', function (Blueprint $table) { $table->id(); $table->foreignId('product_id')->constrained()->cascadeOnDelete(); $table->foreignId('media_id')->constrained('media'); $table->integer('sort')->default(0); }); // after saving the links: app(\NurbekJummayev\LaravelMediaApi\Services\MediaService::class)->markAttached($mediaIds);
Single file — an FK column on the model:
// migration: $table->foreignId('cover_media_id')->nullable()->constrained('media'); $product->cover_media_id = $request->integer('cover_media_id'); // validate exists:media,id $product->save(); app(\NurbekJummayev\LaravelMediaApi\Services\MediaService::class)->markAttached([$product->cover_media_id]);
Auto-marking attached (recommended)
Use the InteractsWithMedia trait so linking flips attached=true automatically:
use NurbekJummayev\LaravelMediaApi\Concerns\InteractsWithMedia; class Product extends Model { use InteractsWithMedia; // FK columns holding a media id → auto-marked attached on save, // and deleted when the model is deleted: protected function mediaColumns(): array { return ['cover_media_id']; } // Pivot media relations → cleaned up (detached + deleted) on model delete: protected function mediaRelations(): array { return ['photos']; } public function photos(): BelongsToMany { return $this->belongsToMany(Media::class, 'product_photos'); } } $product->cover_media_id = $id; $product->save(); // cover media → attached=true automatically $product->syncMedia('photos', $ids); // pivot sync + attached=true
Without the trait, call app(MediaService::class)->markAttached($ids) yourself after linking.
Cascading delete
When a model using the trait is deleted, its media is cleaned up automatically: FK-column media (mediaColumns()) and pivot media (mediaRelations()) are deleted and the pivot links detached.
The physical file is only removed after the surrounding DB transaction commits (DB::afterCommit) — so if the delete is wrapped in a transaction that rolls back, the model, the media row, and the file all survive. The same guarantee applies to MediaService::delete() and the DELETE endpoint. With no active transaction the file is removed immediately.
For soft-deletable parents the
deletingevent also fires on soft delete, so media is removed then too. OverridemediaColumns()/mediaRelations()(or hookforceDeletedyourself) if you need to keep media until a hard delete.
Orphan cleanup
Newly uploaded media are attached=false. Linking flips them to attached=true (via the trait above or MediaService::markAttached($ids)). The scheduled media:purge command (daily) deletes unattached media older than config('media.purge_after_hours') (24h) from disk + DB:
php artisan media:purge --hours=24
Always call
markAttachedafter linking, otherwise the file is purged.
Owner
Each Media row stores an owner_id (set to the authenticated user on upload). The owner relation resolves to config('media.owner_model') — set it to User::class or any other model; null falls back to config('auth.providers.users.model').
$media->owner; // belongsTo config('media.owner_model')
Each upload also records the request ip and user_agent.
Security
Upload handling is hardened against the usual file-upload attacks:
- Content-based type checks. Validation uses Laravel's
mimesrule, which inspects the file's real content viafinfo(plus Laravel's built-in PHP-upload block) — renamingshell.phptoavatar.jpgfails because the content is detected as PHP/HTML, not an image. The storedmimeis the server-detected type, never the client-suppliedContent-Type. - Extension allow/deny list, checked twice.
StoreMediaRequestrejects any blocked extension found in all parts of the filename (soshell.php.jpgis caught) and in the content-guessed extension.MediaService::store()re-checks the extension against the allow/deny list before writing to disk, so even direct (non-HTTP) calls can't drop a.php/.phtml/.htaccess/.exeonto a disk. - No client-controlled paths or names. Files are stored under
Y/m/d/<uuid>.<ext>— the on-disk name is always a random UUID with a sanitised ([a-z0-9]) extension. The original filename is kept only as a displayname, with directory parts and control characters (incl. CR/LF, preventingContent-Dispositionheader injection) stripped. - Private files are sandboxed on the way out.
viewresponses sendX-Content-Type-Options: nosniffand asandboxCSP, so an SVG/HTML file opened directly can't run scripts. - Active content is blocked on the public disk. Public files are served straight by the web server (no controller, so no CSP can be added). Extensions in
public_blocked_extensions(SVG, XML, …) are therefore refused fortype=publicuploads, closing the stored-XSS hole; they remain allowed on the private disk where they're sandboxed.
Deployment note: as defence-in-depth, configure your web server to not execute scripts (PHP, CGI) under the
media/directories. The package never stores executable extensions, but disabling execution there removes the risk entirely even under misconfiguration.
Config
See config/media.php: owner_model, disks, allowed/blocked extensions, public_blocked_extensions, max size, signed-URL TTL (url_ttl), purge window, route prefix/middleware, and per-action upload_middleware/delete_middleware (the can:* permission checks are pulled from here, so you can rename permissions or add throttling without touching the package).
Testing
The package is tested with Pest on top of orchestra/testbench (no full Laravel app needed). CI runs the suite on PHP 8.3/8.4 against Laravel 12.
composer install composer test # vendor/bin/pest composer test-coverage # with coverage
nurbekjummayev/laravel-media-api 适用场景与选型建议
nurbekjummayev/laravel-media-api 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 2 次下载、GitHub Stars 达 0, 最近一次更新时间为 2026 年 03 月 06 日, 在 PHP 生态内属于活跃度较高的组件。
我们在过去多个企业项目中使用过 nurbekjummayev/laravel-media-api 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 nurbekjummayev/laravel-media-api 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
统计信息
- 总下载量: 2
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 25
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2026-03-06