It’d say just as good. I prefer the text based menu of greenshot. The options in this are all icons, so I end up hovering over them all the time to confirm what they are. Works just as well, otherwise.

Nice work!

I think it’s because we know we need to post, but also know we have nothing constructive to add to most things we’re looking at. It’s like people replying all to a birthday email at the office.

They’re all spongeworthy!

I can show you lemmy.world, Shining, shimmering, splendid!

Thank you for this exhaustive investigation!

I don’t have easy access to compose on my NAS, it’s a convenience thing really.

I mean, I know I don’t have to recreate it when I use a normal container, but I’m not clear when using compose

Yes, but the benefit of an official image would be that I wouldn’t have to recreate it when a new version was released, it would update itself when I reload the container.

A Docker image is a read-only template that contains the instructions for building a container. A Docker compose file is a YAML file that defines a set of Docker services.

A Docker image is a static artifact that can be used to create multiple containers. A Docker compose file is a dynamic configuration file that can be used to create and manage containers at runtime.

Docker images are typically used for building and deploying applications. Docker compose files are typically used for managing and orchestrate containers.

That came out of an AI. I can deploy images more easily on my NAS, and I’ve worked with them in the past, so I want an official container so I can deploy it alongside all the other docker containers I have running.

I’ve been thinking about the same thing, and I feel more and more that hosting your own server seems to be the best way to ensure that you get the content that you want without question