• 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: September 10th, 2023

help-circle
  • I was on an old repurposed desktop with 16gb ram and a i7 6700k at the time.

    I haven’t felt that I’ve been missing any features from Gitlab. I do use Woodpecker-CI for runners because Forgejo action’s weren’t working for Docker builds, but I think the Forgejo actions have come a long way since I made that decision; I’ll have to try them out again one of these days.


  • I tried hosting Gitlab for a while, but configuration and upgrades were difficult, and your really have to stay on top of updates due to vulnerabilities. It also used a lot of resources and wasn’t super responsive.

    I moved to Forgejo (a hard fork of Gitea), and haven’t looked back; I cant recommend it enough. It’s fast, doesn’t take a lot of resources, actively developed, and has all the features I need.

    Codeberg is a public instance of Forgejo if you want to try it out first.


  • Regardless of whether you are using a block or an allow list, you have to maintain the list…

    I’m not sure what your point is; if you want to devote your time, effort, and potential liabilities to it, that’s up to you. I just figured I would share a perspective on why I didn’t want to do that.

    I appreciate all the hard work done by instance hosts; using individual Lemmy instances are a privelege, not a right. I would fully understand and not be upset if my home instance were to shut down at a moments notice.



  • I self hosted a Lemmy instance for a little while, but I stopped over concerns of malicious actors posting CSAM which would then get federated over to my server. I don’t have the appetite to deal with that, and I’m glad I shut it down because just a few weeks later there was a big instance of it happening all over Lemmy, and I’m sure I would have had to deal with cleaning it up on my server too. Just something to keep in mind.

    Otherwise though, the setup process isn’t too complex.