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 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.

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.

There are things other than porn that is nsfw. Some workplaces are strict.

Basically I don’t want people posting nude pics/videos of themselves or others. That’s against the spirit of the community.

But other content that might not be acceptable on a work screen would be ok.

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

Thanks for all you do!

I’m assuming you’re using docker.

Make sure you have websockets support turned on.

You might also try to add custom locations under NPM. I made those changes at the same time I made some changes to the “advanced” tab of NPM. I’m not sure which thing fixed it, or maybe it required both. Try this, and if it still doesn’t work, then add the advanced tab settings farther down this reply.

You will need custom locations in your NPM proxy host settings for Lemmy for the following paths.

/api

/feeds

/pictrs

/nodeinfo

They should point to the container that is running the lemmy application, not the UI one, just the lemmy one and to port 8536. If your NPM is not on the same docker network as lemmy, you will need to expose port 8536 on the lemmy container and add it to the lemmyexternalproxy network.

If those changes don’t bring you joy, try also adding the following lines to the “advanced” tab of your NPM proxy host settings for Lemmy.

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $remote_addr;

proxy_set_header X-Forwarded-Host $remote_addr;

real_ip_header X-Real-IP;

real_ip_recursive on;

If anything I have said is confusing to you, please reach out via DM and I’ll try to help.

I hope to see this community take off and take precedence over the one on lemmy.ml. I have been disappointed the past couple of days because most of the IT related subs seemed to be there and they have only been intermittently available and they seem to be having some trouble with federating their content to other instances. It’s not their fault, they are clearly being hugged much too tightly.

Also I know its just the nature of things to have competing subs, even on Reddit it happened. But I’d prefer not to have a split-brain situation with a sysadmin community nor do I want to be forced in to cross posting everything to both communities to increase my chances of engagement.

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?

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.

No worries! I just wanted to let you know why I wasn’t replying where a similar discussion was already in progress.

It’s weird that since I was already subbed to !lemmy@lemmy.ml on my home instance I am able to post and read replies to this post. But I am unable to post or reply to any communities on lemmy.ml I am not already subbed to. For example, on the asklemmy sub, it is marked as “subscribe pending” and I can see the original post you linked to but I can’t see any of the comments. If I go to asklemmy@lemmy ml I can see the original post and ALL the replies but since I’m not a member of the lemmy.ml instance I am unable to reply to it there.

There’s definitely some federation weirdness and lag going on with anything originating from lemmy.ml, hopefully they can get it straightened out.

I actually think that it was a bad idea to host general interest communities that are not lemmy dev related on lemmy.ml. I work in IT and unfortunately the bulk of the active IT communities are all on lemmy.ml, so I am effectively locked out of them until lemmy.ml stops being hugged to death.

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.