this post was submitted on 20 Jul 2023
8 points (90.0% liked)

Lemmy Support

4654 readers
15 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

I have tried the docker, ansible, and scratch methods. I have been troubleshooting for a month now. I have gotten nowhere. I need someone to help walk me through how to deploy a lemmy server because the guides are absolute trash.

Please help. I'm wasting money running this VPS and for literally nothing.

Edit: So, I've tried the ansible method, but I can't access my server this way. It just keeps saying "UNREACHABLE". I have generated a dozen keys, none of them work. I have NO PROBLEMS with ssh in Putty. I can use Putty all day. Putty works fine using my ssh key. Ansible does not. No amount of new keys has made any difference. I have countless keys in my stupid droplet because of this hacky garbage.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

The usecase is for people who want a single-user/small instance or those who are completely new to selfhosting. I'm pretty sure SMTP works if you configure an external one (like Mailgun or SendGrid) which is what most people do (including me) since the SMTP config is done via lemmy.hjson (or in the case of Lemmy-Easy-Deploy, the config.env file). IMO, the only thing that makes Lemmy-Easy-Deploy worse for production use is Caddy which performs worse than nginx in some benchmarks. But I don't think it's that bad.

But if you don't want to use Lemmy-Easy-Deploy, then here's my own documentation on how I installed Lemmy on my server. It's different from the standard Lemmy docker or ansible install where I use nginx natively instead of containerized as this fixes my certbot issues. I'm not an expert on any of this but this is how I got it running.

[–] ZMonster 1 points 1 year ago (1 children)

Thanks for the link. I tried it out and had a problem with the "lemmy.hjson" file. It doesn't look like I would expect, there is a bunch of non-sense. I did the wget command again and checked "config.hjson" and it is identical. So I think there is something wrong with that file.

[–] [email protected] 1 points 1 year ago

Whoops. Sorry about that. I used the wrong link. I fixed it and it should pull the correct config.hjson file now. Feel free to try again if you wish.