-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to serve images from database or s3? #56
Comments
there is no solution for this in the Bundle yet .. but you should be able to implement this using a custom CacheResolver .. if you implement this .. please consider contributing the code back. |
it might be a solution to simply integrate https://github.com/KnpLabs/Gaufrette |
btw, using the stream wrapper available in Gaufrette, it should be fairly transparent for Imagine: simply configure it to use |
You should be serving images from CloudFront, not S3, and doing so using a custom origin: http://aws.typepad.com/aws/2010/11/amazon-cloudfront-support-for-custom-origins.html Makes the whole thing much simpler. |
I've started working on this, I've created a new custom loader to load from the database and will be working on a Gaufrette powered resolver next. https://github.com/neilferreira/LiipImagineBundle Cheers. |
feel free to open a PR even if its not finished in case you want us to give you some feedback already. |
and btw, you don't need to wait for the gaufrette loader to submit the database one. It is even better to keep them in separate PRs to ease review |
I've added a pull request #59, but I'm not sure how to reference it here. |
@neilferreira just write #59 and it will reference it on both ends. thx for the PR .. will check it out today. |
see #63 |
Hi,
I've got a setup where I cannot rely on user uploaded images being on disk, users upload images and I'm storing the file data and mimetype in the database, resizing them and then passing them along to s3.
Have you considered a similar approach?
Cheers
The text was updated successfully, but these errors were encountered: