Keycloak seems complicated, but it's actually not that complicated if you use it for simple OIDC provider.
Just create a new realm, then go to client -> create. Enter your client-id, with openid-connect as protocol. Then, set access type to "confidential", set valid redirect uri to "https://
<your app>
" (or even "https://*" if you're lazy and want to use it on multiple apps). Then hit save and go to the credential tab to copy your client secret. Then head to "users" menu to start adding users to your realm.
That's the basic setup which should be good for home use. The good thing about keycloak is, as you grow your homelab, whatever stuff you may need later can be provided by keycloak. Want some users to have access to app A, but not app B? 2 factor auth? Allow users to login with google account? Heck, allow users to login with another sso provider (chaining)? You can do pretty much anything.
Multiplayer games? Freedom wars, soul sacrifice delta, toukiden, various warriors games (e.g. dynasty warriors, samurai warriors, pirate warriors, etc), Darius burst, Spelunky, dragon's crown,
My favorite single player games are: muramasha rebirth, odin sphere, tearaway, persona 4 golden, rogue ace, luftrausers, rogue legacy, steam world, binding of Isaac. Vita has a strong collection of indie games.
Linux users would post their problems on various forums, but very rarely post their success story. Linux desktop is actually pretty good at this point. Just pick a distro and try it yourself.
I also moved to Debian after years of using Ubuntu Server LTS. No problem so far on those servers for container workloads, the small ones run docker compose, the medium ones run k3s, and a small cluster runs rke2.
The new font smoothing is not the same with the subpixel anti aliasing it replaced. Thin text on non-retina monitors looks worse now than before. Most people probably don't notice it, but for those that do it was a major downgrade.
For some reason google won't implement user-defined site blocklist, even though some other search engines have that feature. You'll have to add -site:website_name manually every time you search.
I guess that's not really possible at the moment because kagi sources their data from other providers where each one of them charges by usage. They're banking on their users to not search as much so they can be profitable, which means they're incentivized to make their search result good so their users won't repeatedly search same topics over and over.
Bluesky finally allows the community to run their own labeller services. This blog post summarize how bluesky federation system works and how the labeler service fit in.
Banana Pi, Orange Pi, etc really took off a few years ago when raspberry pi got harder to find and was marked up like crazy. Even now it's still more cost effective to buy the clones, and they've expanded their sbc offering to include features not available on the original pi.
It's no different than running the app directly, performance wise. It does use more disk storage because the docker image is packaged with everything it needs to run instead of relying on your OS libraries.
Yeah, most file managers don't have "copy to" feature. But, some file managers allow opening multiple panes so copy-paste operation is not as painful when you need to collect a lot of files from different locations in your phone.
redcalcium @ redcalcium @lemmy.institute Posts 20Comments 2,052Joined 2 yr. ago
Keycloak seems complicated, but it's actually not that complicated if you use it for simple OIDC provider.
Just create a new realm, then go to client -> create. Enter your client-id, with openid-connect as protocol. Then, set access type to "confidential", set valid redirect uri to "https://
<your app>
" (or even "https://*" if you're lazy and want to use it on multiple apps). Then hit save and go to the credential tab to copy your client secret. Then head to "users" menu to start adding users to your realm.That's the basic setup which should be good for home use. The good thing about keycloak is, as you grow your homelab, whatever stuff you may need later can be provided by keycloak. Want some users to have access to app A, but not app B? 2 factor auth? Allow users to login with google account? Heck, allow users to login with another sso provider (chaining)? You can do pretty much anything.