I’ve got the domains already - I have a bad habit of buying domains that I never use. It’s really the server part that gets me nervous. I’m not good at that stuff yet, and it’s not really intuitive for me to learn. I know for Mastodon, they have some cloud based servers that they recommend, but Lemmy’s instructions are kinda lacking detail for a newbie like me - and at this time, there’s not really up-to-date YT videos showing you how to do it.
I know that being part of a server seems like a natural fit for someone like me who is totally lost with these things, but it’s kinda frustrating that most larger instances have a ton of rules. I think the one I’m on has rules about lewd content, which is fine, but I feel like one of my comments got blocked from submission when I wrote about how Reddit’s downfall will be similar to Tumblr’s due to their likely eventual banning of that type of content. Maybe some of the words I used were triggering the auto filter or something? But either way, I didn’t like that feeling of censorship.
I didn’t mention the install process in my case, because the box I installed on already had Apache, which conflicted with nginx, and I couldn’t get an equivelant apache config working correctly. So in my case, it took extra steps where I migrated everything from apache to nginx on the box, and stopped using apache. But I did the install using ansible to connect from my PC to the server, and the install process itself wasn’t bad. Copy pasted the config files and made a few relevant changes like DB password, instance name, default admin credentials, and pointing to my existing SMTP mail service. For a personal instance, you could probably exclude that last step though. I already host email for my domain, so the effort to do the extra and make it work was miniscule.
After the config changes, I just put things where the lemmy-ansible repo asked, and ran it as directed. Aside from a few screwups on my part, which were mostly because I was trying to see if I could make Apache work, the install wasn’t too bad. Ansible did the heavy lifting, and if I was installing on a fresh server, I have little doubt it would have given me trouble at all.
If you ever decide to go through with trying, feel free to reach out to me. I’ll be happy to help as much as I can.
I’ve got the domains already - I have a bad habit of buying domains that I never use. It’s really the server part that gets me nervous. I’m not good at that stuff yet, and it’s not really intuitive for me to learn. I know for Mastodon, they have some cloud based servers that they recommend, but Lemmy’s instructions are kinda lacking detail for a newbie like me - and at this time, there’s not really up-to-date YT videos showing you how to do it.
I know that being part of a server seems like a natural fit for someone like me who is totally lost with these things, but it’s kinda frustrating that most larger instances have a ton of rules. I think the one I’m on has rules about lewd content, which is fine, but I feel like one of my comments got blocked from submission when I wrote about how Reddit’s downfall will be similar to Tumblr’s due to their likely eventual banning of that type of content. Maybe some of the words I used were triggering the auto filter or something? But either way, I didn’t like that feeling of censorship.
There’s a guy working on a runs-out-of-the-box Kubernetes install.
I didn’t mention the install process in my case, because the box I installed on already had Apache, which conflicted with nginx, and I couldn’t get an equivelant apache config working correctly. So in my case, it took extra steps where I migrated everything from apache to nginx on the box, and stopped using apache. But I did the install using ansible to connect from my PC to the server, and the install process itself wasn’t bad. Copy pasted the config files and made a few relevant changes like DB password, instance name, default admin credentials, and pointing to my existing SMTP mail service. For a personal instance, you could probably exclude that last step though. I already host email for my domain, so the effort to do the extra and make it work was miniscule.
After the config changes, I just put things where the lemmy-ansible repo asked, and ran it as directed. Aside from a few screwups on my part, which were mostly because I was trying to see if I could make Apache work, the install wasn’t too bad. Ansible did the heavy lifting, and if I was installing on a fresh server, I have little doubt it would have given me trouble at all.
If you ever decide to go through with trying, feel free to reach out to me. I’ll be happy to help as much as I can.