Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T
Posts
9
Comments
51
Joined
3 yr. ago

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

  • It was once great, back in the glory days. Gnome 2 and Compiz, baby! It's still OK too, but not my preferred choice.

  • Yes, it's very similar in Apache, but different enough for me to feel a little out of my comfort zone. I appreciate the tips.

  • Thanks for the tips! That sounds like a great approach. I'll give it a shot.

  • I have reverse proxy configured for Mastodo using Nginx. It's the Lemmy Easy Deploy script trying to bind all traffic on port 443 where I run into problems.

  • Thanks for the advice. I'm actually very experienced with vhosts, but my understanding was that vhosts are an Apache thing and Nginx uses different terminology. Unfortunately I am still very green when it comes to Nginx. What you described is exactly what I intend to implement though, and I believe my Mastodon install is already configured properly for that to work. It's just the Lemmy Easy Deploy script that tries to bind all traffic on port 443 where I run into problems.

  • Interesting point. I hadn't given that any consideration but if my Mastodon/Lemmy plans don't work out I might give it a shot.

  • Except much like your comment, they aren't actually trying to have a good faith discussion.

  • I gave that a try but actually ran into a problem with that too. I setup Mastodon on the same server earlier and was planning to use Nginx server blocks to send traffic for mastodon.fdr8.us and lemmy.fdr8.us to the appropriate destination, but the script failed when it tried to bind all traffic on port 443 and Mastodon is already listening on port 443. I had hoped for both to listen on port 443. This is actually somewhat unfamiliar territory for me as usually I am working with Apache and virtual hosts, but I'm hopeful I can make it work. I am very familiar with Apache virtual hosts and have worked with them extensively. I hope I wasn't crazy to assume I could run Lemmy and Mastodon on the same server on Nginx in a similar fashion.

  • Thanks for the advice. I'm old school and never use Docker, but maybe it's time I get over that. I'm actually out of my element anyway in that I do a lot of self-hosting but up to this point it has almost all used Apache and MySQL rather than Nginx and Postgres. Hopefully someone will come along with a solution for the diesel-async compiling error while I'm at work for the next few hours, but if not I'll give your suggestion a shot this evening.

  • The policy still exists. I am located in California and had to attest to where I am from and how I intend to use the domain.

  • Thanks for the feedback! After days of thinking about it and checking availability it was the best I had come up with so I just went for it. Those urls should work soon if all goes according to plan.

  • And yes, definitely watch those renewal costs. There are some domains that look like a great deal right now with the introductory deals, like .host, but be ready to pay $85 per year at renewal time!

  • That has been my approach so far but I think it's getting pretty picked through. :)

  • I'm thinking general instance, but I don't want a bunch of right wing or religious stuff so I will have some ground rules.

  • They're more expensive, but check out ODroid H3+. Very low power consumption and great options for storage with pcie m.2 and on board SATA, and RAM slots.