Non-string environment variables cause crash. #28
Comments
|
To use integer values, you need to set it in thumbor.conf. It seems thumbor allow_environment_variables() is not able to handle int data types and hence the error. I would recommend opening the issue with thumbor. |
|
Version 3.0 resolves this issue. |
thisismana
added a commit
to thisismana/serverless-image-handler
that referenced
this issue
Jan 28, 2022
* bumped to latest, merged some updates from upstream * - adapted for new key pattern `/$YEAR/$MONTH/$MEDIA_ID/` ignoring file name and always using `image.$EXT` - roundCrops - improved local development by fixing invoke.js and making the logger env-aware * - adapted for new key pattern `/$YEAR/$MONTH/$MEDIA_ID/` ignoring file name and always using `image.$EXT` - roundCrops - improved local development by fixing invoke.js and making the logger env-aware
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was first mentioned in #25, but that original issue had been resolved, so I am repeated this related, but separate issue here.
Thanks to @stevemorad for pointing out that environment variables can be used to set Thumbor conf values. I found that this works for string values, but not for int values, e.g. QUALITY.
I get an error when I set an environment variable with key
QUALITYand value95.Here is the error I'm receiving.
And here is where the error originates from in PIL
Any suggestions on how to work around this? Or do I have to just manually set the value in thumbor.conf as you describe above?
The text was updated successfully, but these errors were encountered: