mirror of
https://github.com/flyimg/flyimg.git
synced 2026-04-25 09:45:50 +03:00
[GH-ISSUE #325] storage_system: s3 option not working #750
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#750
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 @st-pmd on GitHub (Dec 7, 2021).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/325
Originally assigned to: @sadok-f on GitHub.
storage_system: s3 option not working
after following https://github.com/flyimg/flyimg/blob/main/docs/application-options.md#using-aws-s3-as-storage-provider, added all the necessary details in paramters.yml.
I am able to see image pushed to aws bucket but flyimg upload API gives following ErrorException.
Note that with storage_system: local everything is working fine.
@sadok-f commented on GitHub (Dec 7, 2021):
Hi @st-pmd,
Thank you for opening this issue and the details you provided.
I'll investigate it and back to you asap!
Thank you again!
@sadok-f commented on GitHub (Dec 7, 2021):
Hi @st-pmd ,
could you give it a try again with the new release?
thanks
@st-pmd commented on GitHub (Dec 8, 2021):
Thank you @sadok-f for your swift actions.
Let me check & confirm.
@st-pmd commented on GitHub (Dec 8, 2021):
@sadok-f It is working fine. Thanks a ton!
@sadok-f commented on GitHub (Oct 20, 2023):
Hi @st-pmd
I'm wondering if you still use Flyimg in your company/organisation ?
If so, it would be great if you could add your entry here in the Adoperts file
https://github.com/flyimg/flyimg/blob/main/ADOPTERS.md
many thanks!
@jonathanlundstrom commented on GitHub (Feb 16, 2024):
@sadok-f I am still experiencing this issue, although in my forked version (to add S3 endpoint support). The upload to buckets works as intended but then I get this trace:
Any idea why this might still be broken?
@jonathanlundstrom commented on GitHub (Feb 16, 2024):
Also, I've submitted by changes in a PR so that you can review them. They have already been tested with Scaleway and it works as intended, with the exception of the stat error. For reference on endpoint support in Flysystem 1.X you can read here: https://flysystem.thephpleague.com/v1/docs/adapter/scaleway-object-storage/.
See PR: https://github.com/flyimg/flyimg/pull/409
@jonathanlundstrom commented on GitHub (Feb 16, 2024):
@sadok-f, may I ask that this issue be reopened? ☺️
@sadok-f commented on GitHub (Feb 16, 2024):
I'll look into the issue, thanks for reporting it
@sadok-f commented on GitHub (Feb 18, 2024):
@jonathanlundstrom I found the problem related to the issue you reported when using s3 as a storage provider the
Content-Lengthheader should read from thestorage_handlerinstead of reading directly from the generated output.I'll be fixing it soon and releasing and new tag.
@sadok-f commented on GitHub (Feb 18, 2024):
@jonathanlundstrom the fix just got released in the v 1.3.1, can you give it a try ?
thanks
@jonathanlundstrom commented on GitHub (Feb 19, 2024):
Hey @sadok-f! Thanks for merging my changes and fixing the problem. I've checked out the release and can verify that everything seems to work as intended. Now using Scaleway without issues, and other providers should work as well 👌
I think we can close this issue 🖖
@sadok-f commented on GitHub (Feb 19, 2024):
thank you for confirming @jonathanlundstrom
if you're using Flyimg, it would be great if you could add your Organisation here in the Adoperts file:
https://github.com/flyimg/flyimg/blob/main/ADOPTERS.md