this post was submitted on 12 Jul 2025
215 points (97.8% liked)

Selfhosted

49434 readers
727 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
 

A new open-source Single Sign-On (SSO) provider designed to simplify user and access management.

Features:

  • πŸ™‹β€β™‚οΈ User Management
  • 🌐 OpenID Connect (OIDC) Provider
  • πŸ”€ Proxy ForwardAuth Domains
  • πŸ“§ User Registration and Invitations
  • πŸ”‘ Passkey Support
  • πŸ” Secure Password Reset with Email Verification
  • 🎨 Custom Branding Options

Screenshot of the login portal:

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

Sqlite shouldn't lock for read, so unless you are writing something at each access, you can have thousands of concurrent reads. The Sqlite website spells this out, and lists its own self as the proof.

This would mean you could not write logs to the database, you'd have to do it the unixy way and put logs in a text file.