nice rack
Yeah, same here.
Man, paywall is such a pain
Same here, frustrating
Other than simply spinning up a new instance, have you decided on instances to block? A focus for your instance? What type of community do you want to foster?
Thanks! I'll definitely take a look
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.
Yeah, I haven't set it up yet, but if a major instances refuses to federate based on you allowing everything, it'll pressure you to restrict what they require. Almost an abuse of power based on access.
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
Which game?