mirror of
https://github.com/flyimg/flyimg.git
synced 2026-04-25 09:45:50 +03:00
[GH-ISSUE #566] Images Not Being Removed After Serving with cache disabled #202
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#202
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 @eguerracds on GitHub (Feb 25, 2025).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/566
Originally assigned to: @sadok-f on GitHub.
Hello,
I noticed a bug. I received an alert from the host that there is no free space left on the disk, which didn’t make sense to me because I have the /tmp cleanup enabled.
After checking, I found that images in /web/uploads are not being removed after being served.
According to the documentation, setting the following in parameters.yml:
disable_cache: trueshould ensure that images are deleted after being served from /web/uploads
Is this the expected behavior?
Thanks,
@sadok-f commented on GitHub (Feb 25, 2025):
Hi @eguerracds
Thank you for opening this issue!
yes when you put
disable_cache: trueno images should be saved underweb/uploadsfolder.The generated images should be served directly.
let me check this and I'll get back to you.
@sadok-f commented on GitHub (Mar 2, 2025):
Hi @eguerracds again,
I did check and test the disable_cache option, it works as expected.
I'd like to know what Flyimg version you are running?
After enabling the option, did you cleanup your web/uploads folder and check again?
Can you past a URL example for a generated image not being cached?
Thanks!
@eguerracds commented on GitHub (Mar 3, 2025):
Hi @sadok-f,
We are using the latest Flyimg version, 1.7.2.
After confirming that the issue must have been with my Flyimg instance, I tried again, and it seems the problem was with the parameter.yml file. After cloning the repository again and customizing it, everything is working as expected.
I don't know what could have happened with the file. I visually compared it, and it was configured the same way.
Thank you so much.
@sadok-f commented on GitHub (Apr 28, 2025):
Hi @eguerracds
If your company/organisation is using Flyimg, it would be great to have you listed in our ADOPTERS.md file!
Feel free to add your entry — we'd love to highlight your support.
Thank you!