I am experimenting with using forgejo instead of GitHub for my personal projects. So far I like it, however I would like to make it available to the outside world at some point.

I was wondering what kind of traps I should avoid. The following things come to mind so far:

  • Forgejo Actions seem like a massive potential security risk, however I do not intend to enable sign up for other
  • OpenID appears to be a thing for forgejo, I do not know how it works and it seems like it would allow access to my instance even with registering disabled
  • I would put the instance behind a nginx as reverse proxy, but how do you keep bot traffic to a minimum? Anubis?

I feel like there are a ton of things I have not thought of, which is why I am holding off on making anything available without a VPN so far.

  • moonpiedumplings@programming.devEnglish
    2·
    3 days ago
    • oauth, and control sign ups via there. Don’t let people sign up via forgejo itself.
    • anubis, yeah. Or similar.
    • forgejo actions is an optional component… and forgejo users can bring their own actions server. Of course, it’s a risk to them since the server owner could execute code in actions. But yeah.
    • arschflugkoerper@feddit.orgOPEnglish
      0·
      3 days ago

      I definitely want to use forgejo actions, but I am mainly worried about random people being able to execute any code on them. Preferably only approved users can do that.

      • moonpiedumplings@programming.devEnglish
        1·
        6 hours ago

        The way forgejo actions works, is that it is not a universal thing for every repo. Each repo, can have it’s own forgejo actions instance connected to it, running stuff.

        The big benefit of that, is that you can make users bring their own actions servers, and not bother to deploy your own.