mirror of
https://github.com/flyimg/flyimg.git
synced 2026-04-25 01:35:56 +03:00
[GH-ISSUE #151] The alternative resizing method doesn't work #670
Labels
No labels
Docs
Docs
Docs
Security
UnitTest
bug
dependencies
duplicate
enhancement
enhancement
enhancement
hacktoberfest
help wanted
invalid
pull-request
question
stale
version 1
version 2
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/flyimg#670
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @EtreRe on GitHub (Nov 13, 2017).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/151
Originally assigned to: @sadok-f on GitHub.
The alternative resizing method doesn't seem to work.
I have tried it on a local docker environment with no success and the example online have the same issue.
You can see that with or without rz_1 the result is the same :
https://oi.flyimg.io/upload/w_300,h_250,rz_1/https://m0.cl/t/resize-test_1920.jpg
https://oi.flyimg.io/upload/w_300,h_250/https://m0.cl/t/resize-test_1920.jpg
@sadok-f commented on GitHub (Nov 14, 2017):
Thank you for submitting the issue, I'll close it due to the fact that -thumbnail works just like -resize does with a few differences:
If you look to crop the image, you can use the option
c_1if you pass the refresh option
rf_1you'll get the full command generated by ImageMagick in the response header.@EtreRe commented on GitHub (Nov 14, 2017):
My mistake, I thought that rz_1 would force the result to have the size passed in the parameters, filling the rest of the image with background color.
@sadok-f commented on GitHub (Nov 14, 2017):
no worries,
I curious question, do you use flyimg in some a production? or just for testing?
@EtreRe commented on GitHub (Nov 14, 2017):
Testing for now but we are hoping to use it in production if we can make it fit our needs
@sadok-f commented on GitHub (Nov 14, 2017):
Great!
Let us know in case it moves to production!