this post was submitted on 18 Dec 2025
49 points (100.0% liked)

Selfhosted

54096 readers
475 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
49
VoidAuth Release v1.6.0 - Optimization and 1k Stars Celebration πŸŽ‰ (github.com)
submitted 2 weeks ago by notquitenothing@sh.itjust.works to c/selfhosted@lemmy.world
14 comments fedilink hide all child comments
 

In honor of the great RAM ~~price gouging~~ shortage of 2025-2026, this release cuts the memory usage of VoidAuth in half! I noticed that my own instance was pretty thicc at nearly 300MB of memory usage after stabilizing and not doing anything, so decided to do some trimming and optimization.

(Un)Scientific Results:

  • RAM Usage: 280MB -> 150MB
  • Image Size: 660MB -> 360MB

This release also brings better support for public OIDC Clients, but more testing is likely needed to catch edge cases so if something isn't working let me know. Thank you everyone for your engagement and support, I am feeling the love as this project crosses past 1000 stars πŸ₯³. If you are interested, please try it out!

Here are the Release Notes:

What's Changed

Features πŸš€

  • Reduce Image Size and Memory Usage
  • Better support for Public OIDC Clients
  • Allow Native OIDC Clients Non-Reversed-Domain Schemes

Fixes πŸ”§

  • Fixed Issue That Could Cause Stuck Loading Spinner While Prompting to Create Passkey

Docs πŸ“–

  • Docs: add Memos SSO configuration instructions in OIDC guides and fix a typo by @FrostWalk

And a bonus meme:

alien overlord meme with RAM looking down over CPU and RENT

you are viewing a single comment's thread
view the rest of the comments
[–] notquitenothing@sh.itjust.works 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I think technically you might actually not need https termination anymore, it was required when the session cookies were set secure manually but now they should be set automatically if the request protocol was https. You can give it a try just using http or self-signed certs, if you do let me know if it works!

You should be aware though that if you are not using https your password and other secrets will be transmitted unencrypted on that layer, so make sure that your setup is secured/encrypted in some other way like wireguard/vpn tunneling.

[–] irmadlad@lemmy.world 2 points 2 weeks ago

be aware though that if you are not using https

Most definitely using https. I'll give it a go and see what shakes out. Thanks for the help. I'll report back.