mirror of
https://github.com/flyimg/flyimg.git
synced 2026-04-25 01:35:56 +03:00
[GH-ISSUE #209] Feature request: Direct upload endpoint #701
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#701
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 @roman-vohnik on GitHub (Apr 24, 2019).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/209
Hi, first of all - thanks for the great work on this project.
Flyimg is made for image manipulations + serving cached images. But what about new option = to use flyimg only for image manipulations like API service? There can be route / endpoint for direct upload of image in raw format (maybe base64 encoded in POST data). Then source images does not have to be public and downloaded from flyimg. Even works from localhost when developing.
All of this is because our different approach. We have flyimg on separate server as a service and main servers background jobs (in queue) are calling flyimg and saving result images to our storage which is served by our nginx on different domain.
Sounds good to you?
I have a working prototype, but I am not so familiar with silex / symfony. It is something like:
@sadok-f commented on GitHub (May 17, 2019):
Hi @roman-vohnik!
Thank you very much for your request (sorry for this late response), it sounds interesting for us as well.
As I understand for you, you already implement it in your servers?
if you don't mind you can create a PR and we'll review it and check it out.
We'd love to include more people as contributors!
Thank you again!
@github-actions[bot] commented on GitHub (Aug 13, 2023):
This issue is stale because it has been open for 30 days with no activity.
@github-actions[bot] commented on GitHub (Aug 27, 2023):
This issue was closed because it has been inactive for 14 days since being marked as stale.