How do you manage not used images in website like cms?

remix — Fri, 28 Oct 2022 08:04:16 +0000

I'm making website and I have different entities: users, comments, forum threads. It's something like wordpress with simple forum but I built it myself with laravel.

I use storage like s3.

Everything is great but users can upload images in posts, comments, forum threads and have avatar.

With avatar everything is fine:
Event: user uploads avatar
Action: system (cms) will upload image to s3 storage and on success delete previous avatar and change user row in database to use new avatar. Perfecto!

The hardest part is for forum comments, threads.
Event: user uploads image on comment form or thread form.
Action: system (cms) will upload image to s3 storage, add bbcode to textarea in form and add to images table row for uploaded image.

User can after leave page without posting.
User can remove markdown code if he doesn't like image.

So there are some zombie images. Every week I have a cron job to remove zombie images.
System will foreach images in my images table will search that image in comments, threads using lame

SELECT COUNT(*) FROM posts WHERE body LIKE %{image}% SELECT COUNT(*) FROM comments WHERE body LIKE %{image}%

And if it doesn't find it will delete it.

I'm considering to improve it - to loop through posts and comments updated after NOW() and parse with preg_match_all all images used, add to array and then foreach images in my images table will check if image in_array, otherwise delete image.

I'm not sure but this still feels not perfecto.

How do yall manage this kind of things?

Quick Tip. Don't use Fragment.setRetainInstance(true)!

remix — Fri, 16 Nov 2018 15:27:40 +0000

I'm developing android app for few months.

TL;DR
just don't. don't use it. don't create zombie. let them die.

Long story.
I was making nice feed in android app, using fragments. And I thought if I rotate my phone my feed is recreating. That's bad. So I used setRetainInstance(true). And it solved this trouble for short period of time. But then it brings million others. Your fragment that survived rotation is attached to old activity which is dying slowly. (yeah, android is such a retarded in this way but nvm). And so when you try to do smth with it after some period it will die.
Also you can't run any of the method of this fragment from your activity. For example survivedFragment.doSomth() - when you run this android will tell fragment that his context is dead and you can't reattach new activity to it. But even without running command, the dying activity will eventually die and your fragment will too.

So I come to conclusion that you shouldn't use setRetainInstance(true) on a fragment that has at least 1 view object.

Thanks, and shoutout to google: I hate android lifecycle. I think android lifecycle wasted some trillion of human life hours.

DEV Community: remix

How do you manage not used images in website like cms?

Quick Tip. Don't use Fragment.setRetainInstance(true)!