this post was submitted on 22 Nov 2025
375 points (99.5% liked)

Selfhosted

53093 readers
705 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hi guys, I've been working on a self-hostable web analytics platform since the start of this year after being frustrated with Google Analytics and Plausible.

I've packed a bunch of cool web analytics features into Rybbit, but I've tried very hard to keep the interface simple to use,

https://github.com/rybbit-io/rybbit

Check it out!

you are viewing a single comment's thread
view the rest of the comments
[–] LordKitsuna@lemmy.world 1 points 3 hours ago

In its default state i think thats fair. Example docker bypasses most firewalls as it runs before iptables rules process. So if you don't either use 127.0.0.1:port:port (many compose files offered by projects do not do this) or add specialized iptables rules to fix that up you can end up directly exposing services with meaning to or even realizing.

And yeah privilege escalation etc. There are solutions like what you mentioned but it can be a lot of work to set all that up so most people won't