[FEATURE] Streamlined Log

[BassHous3]

Fantastic work, the app is great, while a UI isn't necessary, a cleaner log would be a nice touch.
Similarly to this:

Additionally, it would be nice to have a clean updated image/pull link at the top of the description page.
It is very convenient to install them through CasaOS via the link and having it on top makes it clearer and more straight forward to do so.

Thanks!

[Flaminel]

Fantastic work, the app is great

Thank you!

a cleaner log would be a nice touch

Interesting approach. I'm not sure how this would fit into the logs, but I'll look into it, maybe like some kind of summary at the end. Would having notifications or an API where to pull this kind of data for each item make sense as an alternative?

Additionally, it would be nice to have a clean updated image/pull link at the top of the description page.

I'm not sure I understand where exactly. Is there any GitHub repo you could provide as an example?

[BassHous3]

Would having notifications or an API where to pull this kind of data for each item make sense as an alternative?

• Having notifications that can be hooked to Discord would be amazing. Currently I still get notified when a new grab happened, however I wouldn't know why the grab of same content happened, I can only assume.

• However I was mostly referring to the logs themselves. I use CasaOS and each app has a small button where you can easily view the logs on the go, its very nifty. But as you can see below the logs are quite cluttered, I was suggesting a simplified version of it to have a nice quick overview.

I'm not sure I understand where exactly. Is there any GitHub repo you could provide as an example?

It maybe an unpopular way of installing images/pulls, but its surprisingly convenient.

Here is a repo with an example: https://github.com/thomst08/requestrr
The image link is the same name as repo so its easy (as its on docker): thomst08/requestrr

But in your case its: ghcr.io/flmorg/cleanuperr
And I couldn't find the image link anywhere, only at the bottom of the ReadMe, at the bottom of the Docker compose yaml. I hope I didn't confuse you more.

[BassHous3]

To make it more understandable I was suggesting something like this:

[Flaminel]

I've updated the README and hopefully it's more clear on how to get started.

[BassHous3]

Wow, its looking fantastic, totally wasn't expecting it. Nicely done.