Wow, thank you for these great resources! I will check it out. I really appreciate it!

Sadly, no. My server has been a bit neglected but it's been plugging along and working fine for the most part. I need to upgrade though. And I assume pictrs but to be honest I haven't checked. I just noticed today it was running poorly and checked and the drive is full.

Thanks for the suggestion! As Nix asked, do you happen to know of a guide or any documentation I could reference for this?

Thank you, that SQL command looks like exactly what I'm after! I'm going to give that a shot. I appreciate the help!

Interestingly now that I searched with the URL once and subscribed to a community, I can search with the !community@instance.tld on lemmy.world. Apparently the URL trick is only necessary until federated. Lemmy.world content is showing up in my "all" feed already and things are looking good.

I sort of just got it working. I searched and found a thread where someone said to try entering the full URL. I pasted in the https:// url from a community page on Lemmy.world and it worked. I wonder if that might clue anyone in to what is wrong with my setup. At least I can federate with more instances now though. Woot! Thanks for the help!

Hmm, it sounds like my configuration must be wrong then. I can't search for anything on Lemmy.world, but Lemmy.ml works. Do you have any idea what might cause that?

I'm actually not sure. I remember doing an apt install conky but it's possible that it was already installed and that switched it to manually installed. I also installed tint2 panel, just like the good old days. My panel is extremely minimal. There is no clock, battery info, desktop switcher, or anything except my minimized windows. My battery info, date, time, weather, moon phase, and lots of the usual conky sensor data are available in my conky.

Thanks for the perspective! I am a reluctant newcomer to Docker so I appreciate it. Time for me to get with the times and embrace Docker since that's the most popular installation method for many of my favorite self hosted platforms these days. It might take a while for me to really get used to it though. Since I have this setup and working it will probably remain as is, but I'll make a point to do a pure Docker setup on a similar build in the future.

Teaser pic for the rare fellow Crunchbang enthusiast. Here's a screenshot of my desktop on my $100 USD Asus Vivobook. Crunchbang runs flawlessly on this minimally specced laptop that is basically like a modern day netbook. I'm having a great time with it. I mostly use it to ssh into headless servers from the terminal so I usually just have a web browser and terminal or two open.

I am on a Debian based distro as we speak! I'm using Crunchbang++. For me a perfect operating system is very simple and mostly just stays out of the way. Crunchbang is perfect for that. My setup is very minimal and probably wouldn't be ideal for most users. For most users I recommend Linux Mint, but if you are using Ubuntu and it's working for you there's nothing wrong with that! One of the great things about linux is the huge variety of options of distros to choose from. There's different flavors to suit everyone's needs. What makes this especially great is that under the hood, linux is linux, so for the most part you can use what works for you and not miss out on capability.

Thanks for the suggestion. What would be the benefit of switching to a docker install of Mastodon?

Thanks for pointing that out! In this case I am using subdomains so hopefully I won't run into any issues with that. I recently bought fdr8.us with the intention of creating subdomains under it for my federated projects. Mastodon.fdr8.us and Lemmy.fdr8.us are now live. If I do a kbin instance it will probably follow the same format.

Thank you for sharing your config and advice! I appreciate it. I got it working along with ssl certs installed with certbot and all is well. Cheers!

I didn't plan it that way. I installed Mastodon first and didn't use a Docker install. I configured Nginx and reverse proxy and then tried a non-Docker Lemmy install from scratch. That failed, and I believe the reason was some minor version differences in the dependencies. That's when I asked for advice and got a few recommendations to try the Lemmy Easy Deployment script. I would prefer to have done the from scratch install if there was current documentation and dependencies were available, but if there is I wasn't finding it. The Docker compose Lemmy install method worked well enough though so I'm happy with that.

Thanks for talking through it with me, everyone. I got it working with a Docker compose install of Lemmy and a non-Docker Mastodon install. Reverse proxy was configured manually in nginx. Mastodon.fdr8.us and Lemmy.fdr8.us are now live! I have some fine tuning to do still and a lot of setup, but I'm happy that they are working. Cheers!

This worked great! Thanks again for the advice! When the from scratch install didn't work, multiple people suggested the easy deployment script. For my setup the Docker compose deployment was perfect and offered the opportunity for customization I needed. The easy deployment script does look pretty slick though if someone just wants a turnkey setup and wants to dedicate their whole box to it.

I just got it working. I used a Docker install for Lemmy but not for Mastodon and setup reverse proxy manually. I still have some fine tuning to do, but it works! Woot!

My Mom has been running Mint for over a decade now and I rarely have to remote in and help her with anything. If it passes the works for my Mom test, I think it should work for most people.

I agree with you on principle but I'm typing this from Crunchbang++. On servers I go with Debian every time though.