Hey. I really like the idea of the fediverse and Lemmy and would want to know as a beginner/not so experienced regarding selfhosting what would be the best way to get started? I saw there are vps options, but don’t know of I’m looking in the right direction.
Get a cheap linux VPS. My host provides 4 CPU sd and 8G for 8 eur per month which should be enough for something like 500 users.
Then just run the ansible playbook. It will do everything for you
4 CPU sd and 8G for 8 eur per month
holy crap, that’s cheap!
thanks, in VPS, any red flag I should care for? Privacy, monitoring, etc?
Very low bandwidth caps will be a problem with fediverse.
Other than that, check your steal % once you have the VM. If it’s over 20% consistently, you’re being ripped off.
I have a somewhat related question: is is possible to help the infrastructure by providing a node to host an existing instance?
I don’t wanna have to create and maintain/moderate my own, but would be willing to donate some power and bandwidth to the platform in order to improve performance/geographic distribution etc by having a replica node for an instance/instances of choice.
Thanks
I don’t believe that’s possible. At least, not right now. Happy to be corrected though.
I would also love to help in this way. I have a small home server and an internet connection that has plenty of capacity available.
Personally… it was an experience to say the least. I went down the Docker path for my instance. I’ve tried to keep away from Docker for ages, but here I am.
I’d recommend using the ansible playbook to get it running, as the docker documentation isn’t very detailed and it gets very confusing; especially for a beginner.
The docker documentation is not kept in sync with the docker-compose.yml it asks you to use. So you download the latest one as per instructions, but that’s being regularly updated with no thought to the documentation also being updated. It’s also doesn’t seem aimed at production deployment, just developer test environments. Then there are stupid simple things like the port number being changed in the docker-compose.yml but not in the nginx.conf or the lemmy.hjson. There desperately needs to be better control of that.
There is a lot wrong there and it doesn’t fill me with confidence. It took me 3 hours to piece it all together last night and had to revert to picking bits out of the ansible documentation.
Exactly, I’ve spent ages yesterday and today trying to piece together a set of configs that all work together. I thought it must have been me missing something because the last time I did it everything worked exactly as described in the documentation and it took about ten minutes to get a working instance up and running, but not this time!
It helps slightly (slightly!) if you refer to the configs from the last release rather than the ones on the main branch that are constantly being changed, but even then you’ll have to maybe use the docker-compose.yml from the Ansible repo if you don’t want to build nginx as part of the docker install.
Got there in the end though!
Turns out I can’t upload photos due to the config file they point you at being wrong. Ffs! Direct users to a labelled release and production version. At the moment it’s chaos at the very time it needs to be as seemless as possible.
+1 for Docker, specifically Docker Compose. Lemmy probably isn’t the right container to learn Docker with, but once you have the fundamentals down spinning up Lemmy was pretty seamless.
thanks, wanted to go that route
Make sure you use a Debian base OS, as the playbook uses aptitude to install the dependencies. Also, you can’t use anything over Debian 11, as the way the apt repositories and gpg keys are added, and the pip packages are installed don’t work with the newer OS’.
I found out the hard way lol
Did you start with arch or something 😂 sounds like you went through it lol
Not even ha, just tried to install on Debian 12
I’m using a hetnzer VPS, and the ansible script. It’s working well.
The cheapest way is to get a small vps. If you don’t care to much about the cost and might want to learn more about modern infrastructure practices you could try to getting it running using AWS ECS.
What I’m curious about is running a server only for myself. Am I gonna have problems with being defederated? I’m wanting to run Matrix right next to it on the same domain but they seem much more open to the concept of personal servers.
What I’m curious about is running a server only for myself. Am I gonna have problems with being defederated? I’m wanting to run Matrix right next to it on the same domain but they seem much more open to the concept of personal servers.
it’s alright, i run a personal server with closed registrations. looking for new communities is a bit glitchy, you might need to search a few times before it appears.
Using their docker set up as well and I thought it was quite lean. Out of curiosity, what do you think is overcomplicated about it?
- why use two networks, instead they shouldn’t expose any internal ports if using reverse proxy container within compose (I’m using a separate external load balancer/reverse proxy, so I exposed lemmy & lemmy-backend only);
- stuff like hostname: shouldn’t be needed because it matches service name;
- instead of using generic nginx container image with custom nginx.conf you need to place somewhere manually they should pre-build a container which would work OOTB with the compose setup, this would also solve current situation where nginx.conf and compose file are seemingly maintained separately because they don’t match (i had to change one to match the other);
- a minor thing but i would appreciate environment-based setup instead of needing configuration files (lemmy.hjson) on the filesystem (my ansible-based container deploy system has provisions for this stuff, still its something that i’d rather not have to use…);
- in general compose setup feels like development environment because of all the debugging that is enabled, i think it also tries to build one of lemmy components instead of using an image by default;
it’s all minor stuff, really, but it adds up and people who are not particularly savvy might give up on self-hosting lemmy because of if. so some polish and cleanup might be a good idea.
i know there’s an ansible role too but i haven’t looked through it. i have to do way too much ansible code review & refactoring at work. :)
No, I don’t think so. I’ve just been adding sub…“lemmys” and the flow is a little wonky but it seems to be working well after a few days.
I was considering it.
There is the cost for the vps which would have to be separate in “quarantine” from the rest of our stuff.
Extra cost. $6/ Month sounds cheap but it’s not unless you really feel the need to spend 5+ hours a day troubleshooting the tech side.Then there is the risk of becoming a platform for pedophiles and terrrists.
More time going in that for moderating it and not risk getting our cloud account banned because we hosted illegal stuff - even if it’s by mistake it’s still a risk to get the whole account shut down.
Only way I can see this works is for someone who is knowledgeable enough or has trusted people who are knowledgeable to keep the server clean.
It’s a fun experience I bet but too risky.
Learning to setup infra is a great chance but there are other ways to learn and still not contribute to internet filth or spam.Better a few big sites than 1000 small unmaintained ones.
Running a public instance is 100%, definitely not suitable for someone without experience or at the very least a solid background and a sincere willingness to learn and spend time maintaining it.
A private server for yourself and a group of buds?
There isnt really a reason not to give it a go if youre interested.
