Neos CMS integration of filepreviews.io to generate thumbnails
This package generate thumbnail and extract metadata from different type of document based on the API of filepreviews.io.
This Generator call the FilePreviews.io API to generate Thumbnail for many different file formats. Check filepreviews.io website for more informations.
To use this package you need an account at [filepreview.io]. Create an account if you do not have one yet. Otherwise you can not use this package.
If you already have an account you only have to look up your
API Key and the corresponding
Install the package via composer:
composer require unikka/filepreviews
Configure the API credentials:
Unikka: FilePreviews: apiKey: 'your-key' apiSecret: 'your-secret'
To get the preview images via filepreview.io we use a queue. This means that when you upload a new file to Neos we first create a standard preview image and then request it from the service. When the preview image is available for your website we download it and update the previous preview image.
For the queue to work you need to set it up initially. This is done with the command:
./flow queue:setup filepreview-queue
The command before initializes everything and we get an additional database table
flowpack_jobqueue_messages_filepreview-queue where we list all our thumbnail requests to filepreviews.io.
Now we just have to make sure that a worker is running and processing all our jobs. If an error occurs or a file is not yet ready, the file is put back and queried again.
./flow flowpack.jobqueue.common:job:work filepreview-queue
Like any other Thumbnail Generator, you can change default settings. First step, like mentioned before in the getting stated section, you need to configure your API keys.
Unikka: FilePreviews: apiKey: 'key' apiSecret: 'secret' defaultOptions: format: 'jpg'
apiKey: check filepreviews.io
apiSecret: check filepreviews.io
defaultOptions: check the API endpoint documentation
We use our own thumbnail generator and accordingly different options can be assigned. You can use the FilePreviewThumbnailGenerator with features like the supportedExtensions selectiv for only some specific file formats. For example, it is not very useful to use the generator for images, because Neos can process them itself. Supported Formats from filepreviews.io
Neos: Media: thumbnailGenerators: 'Unikka\FilePreviews\Domain\Model\ThumbnailGenerator\FilePreviewsThumbnailGenerator': maximumFileSize: 2000000 supportedExtensions: [ 'doc', 'docx', 'ppt', 'pptx', 'xls', 'xlxs', 'odt', 'ott', 'odp', 'txt', 'rtf', 'eps', 'psd', 'ai' ]
supportedExtensions: check the official documentation of FilePreviews Supported Formats and enjoy.
maximumFileSize: Default is 2000000
We use the packages Flowpack.JobQueue.Common and Flowpack.JobQueue.Doctrine and these packages come with a lot of own configurations. See the docs of the packages. We use the doctrine backend to have error handling out of the box. But if you want to use redis for instance you can configure that and just replace the className.
Flowpack: JobQueue: Common: queues: 'filepreview-queue': className: 'Flowpack\JobQueue\Doctrine\Queue\DoctrineQueue' maximumNumberOfReleases: 3 executeIsolated: true options: defaultTimeout: 30 releaseOptions: priority: 512 delay: 15
We'd love you to contribute to neos-slick. We try to make it as easy as possible. We are using semantic versioning to have more time to concentrate on important stuff instead of struggling in the dependency or release hell.
Therefore the first rule is to follow the eslint commit message guideline.
It is really easy if you always commit via
yarn commit. Commitizen will guide you.
All PRs will be merged into the master branch. Travis and semantic release will check the commit messages and start building a new release when the analysis of the latest commits will trigger that.
If you have questions just ping us on Twitter or Github.
The package is based on the
Ttree\FilePreviews package. We thank the ttree team for
all the efforts and initial development.
The GNU GENERAL PUBLIC LICENSE (Version 3). Please see License File for more information.