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!

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.

I haven’t used Portainer in a while, but you should be able to click Stacks then +Add Stack and then name your new stack and paste in the docker-compose.yml, then Deploy

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.

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.

Will you be publishing an arm64 docker image for 0.17.4 soon?

Thanks for all you do!

Yes you can subscribe to and read/reply to that community from any lemmy instance. You just need to add it if the instance doesn’t already federate with it.

Go to ‘Communities’ at the top of your instance homepage then in the search bar put the url of the community you want to add. (example: https://beehaw.org/c/programming)

This next part is undocumented, and might just be a bug. But this is the magic part.

On the next page, change the top search dropdown from Communities to All.

You will see the community you want to sub to in the results. It will say something like.

Programming@beehaw.org - 0 subscribers

Click it, then on the top right pane click “Subscribe”

Done

Making specialized instances does not in any way make hopping around necessary. If you join a specialized instance that doesn’t already sub to the communities you want, you just add them.

Example: I join a Star Trek themed instance that has a bunch of locally created star trek communities. I want to sub to all those, but i ALSO want to sub to the homelab community on beehaw. I just subscribe to !homelab@beehaw.org FROM the star trek instance I am a member of. That star trek instance will then start syncing the homelab content from beehaw and you can read and reply from the star trek instance.

Conversely, if someone has an account on beehaw.org and they want to read a star trek community based on that star trek instance, they just need to sub to it FROM beehaw.org.

I didn’t even see that discussion because I wasnt subbed to asklemmy and I haven’t been able to sub to any communities on lemmy.ml for two days now. I can’t reply to you there as a result. So while your hesitancy is warranted, you still have the same problem when a place like lemmy.ml hosts the communities you enjoy but then can’t handle the load. The end result is the same as it would be if a themed instance was unavailable or suddenly shut down.

Just plain old netinst installed Debian with XFCE. It just works.