Selfhosted

57954 readers

941 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

hosting forgejo publicly (feddit.org)

submitted 20 hours ago by arschflugkoerper@feddit.org to c/selfhosted@lemmy.world

17 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] emerald@lemmy.blahaj.zone 6 points 18 hours ago (1 children)

I run a forgejo server on the internet for myself so here's my two cents.

OpenID or any other log in method is just a way to log in to an account on the forgejo server. With registrations disabled it shouldn't be able to create an account, so there should be no issue. All the extra auth methods also need to be configured and are disabled by default.

Bot traffic can be pretty horrendous once they find your server, I'd say Anubis is basically a requirement at this point. I would also strongly recommend setting up fail2ban for http and ssh, and disabling ssh password auth.

[–] arschflugkoerper@feddit.org 1 points 18 hours ago (1 children)

Ah I see, I kinda assumed that OpenID would allow anyone with an OpenID server to just log in. That seemed like it would cause immediate spam issues. It would definitely be nice if I could allow users to create issues or stuff like that at some point. I will definitely have to take a look at fail2ban before I make it available. Thank you.

[–] EncryptKeeper@lemmy.world 1 points 5 hours ago

No OpenID is configured against your OpenID server