Package Data | |
---|---|
Maintainer Username: | expstudio |
Maintainer Contact: | expstudio@gmail.com (Watee Wichiennit) |
Package Create Date: | 2017-09-01 |
Package Last Update: | 2017-09-11 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-15 15:08:20 |
Package Statistics | |
---|---|
Total Downloads: | 3,880 |
Monthly Downloads: | 0 |
Daily Downloads: | 0 |
Total Stars: | 0 |
Total Watchers: | 2 |
Total Forks: | 0 |
Total Open Issues: | 0 |
Lumen-Stapler is a Stapler-based file upload package for the Lumen framework. It provides a full set of Lumen commands, a migration generator, and a cascading package config on top of the Stapler package. It also bootstraps Stapler with very sensible defaults for use with Lumen. If you are wanting to use Stapler with Lumen, it is strongly recommended that you use this package to do so.
Lumen-Stapler was created by Watee Wichiennit.
This package currently requires php >= 5.4 as well as Lumen >= 5.4. If you're going to be performing image processing as part of your file upload, you'll also need GD, Gmagick, or Imagick (your preference) installed as part of your php environment.
Lumen-Stapler is distributed as a composer package, which is how it should be used in your app.
Install the package using Composer. Edit your project's composer.json
file to require expstudio/Lumen-stapler
.
"require": {
"laravel/lumen-framework": "5.4.*",
"expstudio/lumen-stapler": "1.0.*"
}
Once this operation completes, the final step is to add the service provider.
For Lumen 5.4, Open config/app.php
, and add a new item to the providers array:
$app->register(Expstudio\LumenStapler\Providers\LumenStaplerServiceProvider::Class);
In your models that are using Stapler, change use Codesleeve\Stapler\Stapler
to use Codesleeve\Stapler\ORM\EloquentTrait
. Your models will also need to implement Codesleeve\Stapler\ORM\StaplerableInterface
.
If you published stapler's config, you'll need to rename config folder from app/config/packages/expstudio/stapler
to app/config/packages/expstudio/lumen-stapler
.
Image processing libraries are now referenced by their full class name from the Imagine Image package (e.g gd
is now reference by Imagine\Gd\Imagine
).
In your s3 configuration, instead of passing 'key', 'secret', 'region', and 'scheme' options, you'll now need to pass a single 's3_client_config' array containing these options (and any others you might want). These will be passed directly to the s3ClientFactory when creating an S3 client. Passing the params as an array now allows you to configure your s3 client (for a given model/attachment) however you like. See: http://docs.aws.amazon.com/aws-sdk-php/guide/latest/configuration.html#client-configuration-options
In your s3 configuration, instead of passing 'Bucket' and 'ACL', you'll now need to pass a single 's3_object_config' array containing these values (this is used by the S3Client::putObject() method). See: http://docs.aws.amazon.com/aws-sdk-php/latest/class-Aws.S3.S3Client.html#_putObject
The ':Lumen_root' interpolation has been changed to ':app_root'
In the document root of your application (most likely the public folder), create a folder named system and
grant your application write permissions to it. For this, we're assuming the existence of an existing User
model in which we're going to add an avatar image to.
In your model:
use Codesleeve\Stapler\ORM\StaplerableInterface;
use Codesleeve\Stapler\ORM\EloquentTrait;
class User extends Eloquent implements StaplerableInterface {
use EloquentTrait;
// Add the 'avatar' attachment to the fillable array so that it's mass-assignable on this model.
protected $fillable = ['avatar', 'first_name', 'last_name'];
public function __construct(array $attributes = array()) {
$this->hasAttachedFile('avatar', [
'styles' => [
'medium' => '300x300',
'thumb' => '100x100'
]
]);
parent::__construct($attributes);
}
}
Make sure that the
hasAttachedFile()
method is called right beforeparent::__construct()
of your model.
From the command line, use the migration generator:
php artisan stapler:fasten users avatar
php artisan migrate
In your new view:
<?= Form::open(['url' => action('UsersController@store'), 'method' => 'POST', 'files' => true]) ?>
<?= Form::input('first_name') ?>
<?= Form::input('last_name') ?>
<?= Form::file('avatar') ?>
<?= Form::submit('save') ?>
<?= Form::close() ?>
In your controller:
public function store()
{
// Create and save a new user, mass assigning all of the input fields (including the 'avatar' file field).
$user = User::create(Input::all());
}
In your show view:
<img src="<?= $user->avatar->url() ?>" >
<img src="<?= $user->avatar->url('medium') ?>" >
<img src="<?= $user->avatar->url('thumb') ?>" >
To detach (reset) a file, simply assign the constant STAPLER_NULL to the attachment and the save):
$user->avatar = STAPLER_NULL;
$user->save();
This will ensure the the corresponding attachment fields in the database table record are cleared and the current file is removed from storage. The database table record itself will not be destroyed and can be used normally (or even assigned a new file upload) as needed.
This package provides a fasten
command that can be used to generate migrations for adding image file fields to existing tables. The method signature for this command looks like this:
php artisan stapler:fasten <tablename> <attachment>
In the quickstart example above, calling
php artisan stapler:fasten users avatar
followed by php artisan migrate
added the following fields to the users table:
The refresh
command can be used to reprocess uploaded images on a model's attachments. It works by calling the reprocess() method on each of the model's attachments (or on specific attachments only). This is very useful for adding new styles to an existing attachment when a file has already been uploaded for that attachment.
Reprocess all attachments for the ProfilePicture model:
php artisan stapler:refresh ProfilePicture
Reprocess only the photo attachment on the ProfilePicture model:
php artisan stapler:refresh TestPhoto --attachments="photo"
Reprocess a list of attachments on the ProfilePicture model:
php artisan stapler:refresh TestPhoto --attachments="foo, bar, baz, etc"
Before you submit an issue or create a pull request, please take a look at the Troubleshooting Section section of the Stapler package. There's a very good chance that many (if not all) of the issues you're having with this package are related to the base stapler package and have already been addressed there.
This package is always open to contributions: