The codebase and documentation seems to be a little floored. When you build from the repo it will not install and fails at the s3 bucket stage every time.
If you install using the AWS hosted template this will work but you can only get it to work if you base64 encode or store every image in the root of the bucket. base64 encoding data to get an image resized is not practical and not how pretty most people will want to use a on the fly image service.
The url based (Thumbor style paths) are key to getting the most value out of this type of service but you need to be able use a object which is not in the base of the bucket.
When do you think the next release will be with a fix to the image paths? or improved documentation and steps to fix the s3 bucket issue when using the repo
The codebase and documentation seems to be a little floored. When you build from the repo it will not install and fails at the s3 bucket stage every time.
If you install using the AWS hosted template this will work but you can only get it to work if you base64 encode or store every image in the root of the bucket. base64 encoding data to get an image resized is not practical and not how pretty most people will want to use a on the fly image service.
The url based (Thumbor style paths) are key to getting the most value out of this type of service but you need to be able use a object which is not in the base of the bucket.
When do you think the next release will be with a fix to the image paths? or improved documentation and steps to fix the s3 bucket issue when using the repo