cruxinator/laravel-attachments

Unified way to handle media attachments to Laravel models

dev-master 2023-07-03 00:58 UTC

Requires

• ext-bcmath: *
• ext-gd: *
• ext-json: *
• cruxinator/laravel-html: *
• cruxinator/laravel-package: *
• cruxinator/responsemodels: dev-master
• cruxinator/singletableinheritance: *
• laravel/framework: 6.*|7.*
• php-ffmpeg/php-ffmpeg: *

Requires (Dev)

• ext-pdo: *
• ext-sqlite3: *
• infection/infection: *
• league/flysystem-sftp: ^1.0
• mikey179/vfsstream: *
• nunomaduro/collision: ^3.2
• nunomaduro/larastan: >=0.4.0
• orchestra/database: ^3.0|^4.0|^5.0|^6.0|^7.0
• orchestra/testbench: ^3.0|^4.0|^5.0|^6.0|^7.0
• phpstan/extension-installer: *
• phpstan/phpstan-deprecation-rules: *
• phpstan/phpstan-phpunit: *
• phpunit/phpunit: ^7.0|^8.5|^9.0

MIT

• Chris Harris
• Alex Goodwin

• laravel
• attachments
• cruxinator

README

This is where your description should go. Limit it to a paragraph or two. Consider adding a small example.

Support us

Installation

You can install the package via composer:

composer require cruxinator/laravel-attachments

You can publish and run the migrations with:

php artisan vendor:publish --tag="laravel-attachments-migrations"
php artisan migrate

You can publish the config file with:

php artisan vendor:publish --tag="laravel-attachments-config"

This is the contents of the published config file:

return [
];

Optionally, you can publish the views using

php artisan vendor:publish --tag="laravel-attachments-views"

Usage

$variable = new VendorName\Skeleton();
echo $variable->echoPhrase('Hello, VendorName!');

Testing

composer test

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• :author_name
• All Contributors

License

The MIT License (MIT). Please see License File for more information.