- cross-posted to:
- opensource@lemmy.ml
- cross-posted to:
- opensource@lemmy.ml
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:
I think technically you might actually not need https termination anymore, it was required when the session cookies were set
securemanually 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.
Most definitely using https. I’ll give it a go and see what shakes out. Thanks for the help. I’ll report back.