Perhaps you will find something interesting here. https://www.youtube.com/channel/UCmkeI_NrzwcIgZYHCFSxXTQ
In the real world, the "drugs and/or brainwashing" can be replaced with poor education and fixation on cults of personality and outrage culture pushed into their brains and eyeballs through 24/7 media coverage. The wolves are the media, the billionaires, and others in power who need the sheep to move and vote in the ways that is often against their own best interest. Sorry to get a little political, but those factors are in play no matter what the ideology is.
I think that there is a combination of all those things. I believe there are Village agents, "wolves among the sheep", who influence villager actions. I also believe that many of the villagers have long been broken via drugs and/or brainwashing. This makes them pliable to anything that the agents embedded in the community wants them to do. I think that the Village probably doesn't take on more than a handful of people like #6 at any one time for fear that they might team up and influence an easily influenced group of villagers by emulating what the embedded agents do. TLDR, I think most of the villagers are more or less brainwashed lemmings and the ones that aren't are agents.
I do appreciate your feedback, but I think at a minimum that anyone trying to run a Lemmy instance in Docker should know how to install docker and docker compose and how to run basic commands like docker compose up -d
. There are many tutorials out there for doing just that and I'm not trying to reinvent the wheel. Once you have gotten that part done my document kicks in and picks up where the official documentation is currently lacking (in my opinion).
I do explain a lot, but I did my best to explain it in terms that most anyone could understand.
I will take your feedback to heart and maybe try to write a step by step tutorial for people who are completely new to Docker as well.
I don't use unraid, so I'd have no way to develop and test it. But I think all you really need to do is install docker and docker compose and then just follow my guide.
Thanks for your comment, but I don't see much value in pulling a new copy of the docker-compose.yml from the Lemmy GitHub. The only things I would be updating when Lemmy updates is the tag/version. If they added new environment variables some time in the future I could certainly take a look at their updated compose file to see the changes but I wouldn't want to pull it down and replace my custom compose.
I specifically don't care for their (Lemmy devs) choices for logging, docker networking, and the built in nginx, so removing and simplifying all that was my main goal. Everyone has their own way of doing things, and this is mine.
I will probably take a look at your Traefik configs and add them as a separate document for those that don't want to use NPM. My goal is to add a subsection for most of the current revproxy choices.
I do not recommend using Ansible. It adds additional requirements and complexities that are unnecessary. Ansible is a great tool for managing multiple servers and software installs, in my opinion it is not the right tool to install Lemmy on a single instance. My install instructions require only that you have docker and docker compose installed.
That said, you could easily replace the docker-compose.yml that Ansible set up for you with the one I am providing. Just don't run Ansible against your server again or it will wipe out your changes.
It's one of the few remaining intact and operating Rockafire Explosion animatronic band. https://en.wikipedia.org/wiki/The_Rock-afire_Explosion
Seems like the best thing to do would be to run that on a daily schedule and also ideally something done in the ui. I worry for those admins that just "followed the recipe" to get a Lemmy instance up and running but lack any real sysadmin ability.
I think theres probably a big overlap between the novice admins and the instances where the admins are unaware they are getting flooded with bot registration.
I only have com/net/org domains, so I never noticed that. But you've provided good information. There is a list of CloudFlare supported TLD's here https://www.cloudflare.com/tld-policies/
@tet42
@ka.tet42.org