Feedly is the closest thing to Google Reader that I’ve found.

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.

I tried doing that with a previously unsearched/unsubscribed community as a test on my own instance, and I got a 404: couldnt_find_community error when clicking the link. As you stated, it seems like in most cases that special link will not work unless someone has previously manually searched for the same community in your instance.

I think I’d rather link directly to the instance for the community than get a 404 error. For most people, getting the 404 will just deter them from proceeding further.

Perhaps it would be best to include both links in a post?

I was explaining it to a friend today, and I came to the conclusion that Lemmy is a LOT like the old FIDOnet message network that was used on BBS’s.