expstudio / stapler
Fix AWS 3.0 version of Elegant and simple ORM-based file upload package for php.
Requires
- php: >=5.4
- doctrine/inflector: ~1
- imagine/imagine: ~0.6.2
- symfony/http-foundation: ~2.3|~3.0
Requires (Dev)
- aws/aws-sdk-php: ~3.0
- illuminate/config: 4.*|5.*
- illuminate/database: 4.*|5.*
- mockery/mockery: 0.8.0
This package is not auto-updated.
Last update: 2024-12-13 22:01:57 UTC
README
#Stapler
Note: If you've previously been using this package, then you've been using it with Laravel. This package is no longer directly coupled to the Laravel framework. As of 1.0.0, Stapler is now framework agnostic. In order to take advantage of the Laravel specific features provided by the previous Beta releases (service providers, IOC container, commands, migration generator, etc) , I've created a separate package specifically for the purpose of using Stapler within Laravel: Laravel-Stapler. If you're using Stapler inside a Laravel application I strongly recommend you use this package (it will save you a bit of boilerplate).
Stapler is a php-based framework agnostic file upload package inspired by the Ruby Paperclip gem. It can be used to add file file uploads (as attachment objects) to your ORM records. While not an exact duplicate, if you've used Paperclip before then you should feel quite comfortable using this package.
Stapler was created by Travis Bennett.
Requirements
Stapler currently requires php >= 5.4 (Stapler is implemented via the use of traits).
Installation
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 codesleeve/stapler.
"require": { "codesleeve/stapler": "1.0.*" }
About Stapler
Stapler works by attaching file uploads to database table records. This is done by defining attachments inside the table's corresponding model and then assigning uploaded files (from your forms) as properties (named after the attachments) on the model before saving it. Stapler will listen to the life cycle callbacks of the model (after save, before delete, and after delete) and handle the file accordingly. In essence, this allows uploaded files to be treated just like any other property on the model; stapler will abstract away all of the file processing, storage, etc so you can focus on the rest of your project without having to worry about where your files are at or how to retrieve them.
Key Benefits
- Modern: Stapler runs on top of php >= 5.4 and takes advantage of many of the new features provided by modern php (traits, callable typehinting, etc).
- Simple: Traditionally, file uploading has been known to be an arduous task; Stapler reduces much of the boilerplate required throughout this process. Seriously, Stapler makes it dead simple to get up and running with file uploads (of any type).
- Flexible: Stapler provides an extremely flexible cascading configuration; files can be configured for storage locally or via AWS S3 by changing only a single configuration option.
- Scalable: Storing your assets in a central location (such as S3) allows your files to be accessable by multiple web instances from a single location.
- Powerful: Stapler makes use of modern object oriented programming patterns in order to provide a rock solid architecture for file uploading. It's trait-based driver system provides the potential for it to work across multiple ORMS (both Active Record and Data Mapper implementations) that implement life cycle callbacks.