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.
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.
+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.
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'.
Did you get it to run on docker? My personal instance is running, federation and community search semm to be working but when I subscribe to something it just says "pending" and does not seem to actually go through
I did, yes. It took me a few hours of troubleshooting though, spanned across two days. I'm using Nginx Proxy Manager instead of the Nginx proxy that comes with Lemmy, but it all translates similarly. I also followed this guide on YouTube.
If it's sitting there saying "pending" for your subscriptions, it may be that the "proxpass /" location ports are off by one. It'll look like it's federating properly, but really it isn't. That was one thing I noticed with the documentation/examples; things were off and not updated. Check my screenshot attached for what I mean. The documentation/example config for the proxy lists the Lemmy-ui port as 1235, but it's actually 1236.
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.
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.
e: one thing i have to note is that docker-related documentation is somewhat inaccurate and, in my opinion, their setup is a bit overcomplicated.
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.
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.
Like this it does make sense for learning and it can be done locally on a regular PC. No need to even have it running more than 5h/ week.
Only start it when trying something.
There are other more interesting things to learn and setup. Something like a honeypot.
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.