Promotion of other Lemmy instances (beehaw.org)

submitted 2 years ago by spaghetti_carbanana@beehaw.org to c/support@beehaw.org

6 comments fedilink hide all child comments

Hi beehaw admins! Thanks for this platform you’ve given us all. I’m wondering what your stance is on promotion of other Lemmy instances here?

In the interest of decentralisation and keeping the community robust, I’m considering standing up my own instance of Lemmy. I’m fortunate enough to have plenty of equipment at my disposal to run it and the know-how to make it resilient and scalable (not quite big social network tier, but I don’t want it to be that anyway).

I just wanted to ask here first before I go shamelessly self-plugging around the place.

Feel free to ask questions if you’re curious or your answer is “it depends”. Thanks!

you are viewing a single comment's thread
view the rest of the comments

[-] spaghetti_carbanana@beehaw.org 1 points 1 year ago

Coming back to update this thread after having stood up the server which I've called Krab Borg. All are welcome to join. As far as deploying it went, "Pretty easy" was subjective in this case; Docker itself is not inherently difficult to work with once you understand it, however Lemmy was super vague on how to deploy it.

A couple of things I got stitched up on that I hope save someone else the pain:

The docker compose file in the "main" Github branch is built for a non-production instance, so a bunch of unnecessary stuff is in there, and a bunch of necessary stuff isn't. I basically took the compose file from the 0.17.4 tag here. I also generated a long password to use as the API key for pictrs.
I use an external NGINX server (running on a different server to Lemmy) as the SSL termination point and internet-facing reverse proxy. I had issues with federation "sort of" working; some sites would federate while others wouldn't (I'd find the communities but get "Subscription Pending" when subscribing). It turns out I didn't put the full intermediate SSL certificate chain into my certificate file, so even though the site appeared to be working, some servers wouldn't accept the cert. This was hinted to me when I saw in packet traces that the remote side was sending RST packets after trying to subscribe to a community. Once I fixed the certificate chain in the file, this problem went away (Note - if you use Lets Encrypt this shouldn't be a problem).
This is well documented but just to really emphasise it - searching for a community will pull in ~50 of the most popular posts and no comments to give you something to start. You will not receive any new posts (and their comments) unless you actually subscribe to the community. I created a "sub booster" account which I used to subscribe to all of the communities I searched for, so as not to fill my own feed with too much that isn't relevant to my interests but to get content flowing into the server and make it diverse enough.

So far all is going well and now it's over to the more "operational" side, like figuring out how to get people in, what communities I should create vs bring in from external sites, etc.

If you'd like to know more about the instance, setting it up or the architecture it sits on, I'm more than happy to share the info or help you if you're stuck setting up your instance (I work in IT/Security which helps).