I don't hate it. It makes room to tell new "old" stories without just completely dismissing canon. The idea of a "fixed point in time" is a concept that I think originated with Doctor Who. The Strange New Worlds concept is similar, but instead of a fixed point its a fixed event or fixed outcome.
I do wonder though, how much of this "time pushing back" is actually that? Or is it actually just the "Federation Time Cops" from the far future making sure things happen even if someone successfully meddles with history. I actually kind of hate the concept of time travel being a thing in Star Trek. Leave it to shows like Doctor Who.
Love it! Thanks for sharing!
Consider joining my Show Me What You Got community to share this there. This is exactly the kind of content I'd love to see there.
https://ka.tet42.org/c/showmewhatyougot
This is a sub to show off your stuff. Whatever it may be. Do you make fine handmade furniture? Do you have a nice record collection? Do you have a special talent? Did you take a picture/video of something interesting? Show me what you got! Upvoting and downvoting is encouraged to drive the coolest stuff to the top.
Please no porn.
My musical tastes are fairly obvious. Classic rock, metal, prog. Show me what YOU got!
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/
I have most of my domains on Google, but also have a couple on CloudFlare. I suppose I will just move them all to CloudFlare. They offer free WHOIS privacy and several other features for free. For those of you self hosting on a dynamic IP, there's a pretty good API that you can use for DNS updates.
Gorgeous! Is there any chance that you have more build details? A list of parts needed or even perhaps photos or video of your work would be great!