If you want to host and manage your own Lemmy instance but are intimidated by the technical requirements, I can help!
I am a software developer by craft and a linux system admin by hobby. I cannot commit to moderating and managing my own instance, but I would be glad to help someone with the technical aspects.
The most common complaint I saw in Reddit and here about switching to Lemmy is the difficulty of setting it up, so I thought I would help bridge this gap.
While I have never hosted my own instance before, I already checked the setup guide and it looks pretty simple to me, so I am confident I can do it. Please feel free to comment or DM.
It would be great if you can comment general questions. I can then respond to you here and maybe others will see it and know how to host their own instances too.
An up to date step by step instruction for docker, ansible, or scratch setup would be a fantastic step in the right direction. I'm not a complete moron, but I feel the current guides are lacking. There's a lot of assumptions on the admins knowledge of the associated systems beforehand. As someone else said, the first to make a turnkey solution... hot dog. Would absolutely blast adoption into space.
I likewise have a similar background to the OP. I wouldn't say I struggled (thanks to the Matrix chat room), but the docker instructions straight up didn't work a couple of days ago. I and another guys submitted a couple of PRs and I think the instructions should at least work for common setups now, but the edges are very rough.
By far the best way to contribute IMO is submitting PRs. The devs seem very willing to take contributions without making you jump through hoops.
I feel like there's a lot of money on the table for the first person to set up a turnkey hosting platform for Lemmy. Something like MoltenHosting but for Lemmy instead of Foundry.
Thanks for offering your knowledge!
I successfully set up and instance using their docker installation guide. However I was never able to get the smtp server to work.
I first tried to add postfix to the docker-compose file like they have in the ansible installation example on github, but that didn't work. Just trying to add an email address to my account would stall the UI with a spinning animation on the Save button.
I then tried to update the hjson config file by adding my sendgrid api credentials and removing postfix from docker compose. That gave me the same result.
At that point I kinda gave up and deleted my vps. I don't have access to my error logs anymore, but I can spin up a new vps to try to get the same errors again if needed.
A lot of VPS providers block port 25 (and other email ports) because they don't want people to set up bot spam mail servers on their services. Could that be the issue?
If you have Cloudflare you can set up an email alias for incoming email and then create a secondary Gmail address on top of your existing one if you go to 'Settings > Accounts and Import > Send mail as' and add another email address (not an alias). You will likely need to create a Gmail app password if you use 2FA.
If done it this way for a few services beyond Lemmy and it's worked well so far. This way you're also using a Gmail account technically so you can hopefully avoid blacklists and spam filters.
CPU requirements for Lemmy hosting are minimal. Memory is useful - you'd want to use the Pi 4 with either the 4GB or 8GB RAM, anything less than that will work but you'll be running the risk of difficulties if the server gets busy.
You'll also need plenty of storage, especially if people are going to start uploading media to your Lemmy host. Given that a Pi runs off an SD card you might well find yourself running out of storage space - I'd recommend attaching a USB storage device for the reassurance in that respect.
I've been playing with my own single-user instance here using Docker. Mostly I just followed the Lemmy docs. It's been nice & responsive and takes barely any resources, so far. I think this system can really benefit from a lot of small instances to spread the load.
Perhaps write a thread, with step-by-step text and photos/screenshots per platform? And then the next one to do would be a step-by-step video?
Example, I'm not technically minded, but have an Unraid box with a 1Gb connection. There are extra steps there that I'm aware of but have no idea how to do because it's over my head.
Hi there - thanks for posting. I’m serving lemmy (ansible install) on nginx from Ubuntu 22.04 and I’m seeing this weird problem sometimes where the submit button is not enabled on the “create post” form. Sometimes it works but then it inexplicably stubbornly refuses to - I am not seeing any apparent error show up in the console, nothing in the lemmy or nginx logs (naturally, because the HTML form isn’t submitting to the server because the submit button's disabled). Happens in different browsers, tried restarting nginx, rebooting, nothing seems to fix it. Now, my addled brain does recall seeing something about Ubuntu 22.04 having some issues with Lemmy and perhaps that’s what I’m seeing - it’s just weird and I’ve never seen a web app do this before - any ideas? The url is quex.cc and you’re welcome to test there if you like, but I'm really just looking for any suggestions for investigation before I start thinking about moving to a different OS.
yes, good suggestion, thank you - although before I do I'm going to spend a bit of time to see if I can isolate the problem - I just tested it from a mobile device and the local PC browser and it's working now. I used the exact same url, text and everything to create the post and I didn't change anything - didn't reboot, didn't even restart the browser. Except for the fact that it's intermittent, it looks like some kind of js or css problem, but I need to replicate it and if I do that, I'll probably be able to figure it out.
I was playing with the idea of spinning up a VPS through AWS lightsail since the bundled package it provides seems to be cheaper than configuring an EC2 instance/other requisite resources running 24/7.
What has been people's experience regarding:
Monthly data upload rates (since most cloud providers charge internet egress per gigabyte)
Being a highly technical guy, I struggled to get everything running on the server that I am hosting other things on. The biggest hurdle was letsencrypt, but other things weren't working quite right. I ended up just paying for a new ubuntu vps so I can run the ansible playbook (I use arch linux everywhere else). That turned out to be super simple and "just worked".
The thing I struggled with the most was adapting the provided docker-compose.yml for my Caddy setup.
I am using caddy-docker-proxy, which I absolutely love but their documentation is not the greatest for matchers.
If anyone else wants a super basic Lemmy instance running on Caddy with their domain on Cloudflare here is a docker-compose.yml
Please make sure you update your lemmy.hjsonhostname field to match the domain you used in the docker-compose.yml for the caddy labels
If you're not using Cloudflare you can replace build: . (and not use the Dockerfile I provided below) in the caddy service with image: lucaslorentz/caddy-docker-proxy:ci-alpine (and remove the caddy.acme_dns label) and I believe it will fall back to Let'sEncrypt
Anyone know if setting up an instance via a shared Hostgator server is possible? I already pay for a plan for my personal site so wondered if I could add on a new domain plus a partition to it and take advantage to make my own instance for posting and browsing myself.
It's easy from the docker from what I can tell, the bare metal / vps is a bit more as more manual pieces but nothing too crazy. I just submitted a pull request for the admin guide so that should help a bit for less head bashing... Though my instance doesn't seem to be federating so that's a new problem for tomorrow.
My two cents, I had a wobbly Lemmy instance setup that couldn't do HTTPS, federation, and stay stable all at once. It was always 1 or 2 of those 3 at best.
Switched my instance to kbin, which took about a half hour of CLI and after that has been a joy. It's just younger and admittedly less feature packed right now.