Nice, glad you got it working!
curled
- 0 Posts
- 4 Comments
Maybe the example you posted is incomplete, but it looks like you haven’t defined a secret key like the official example does. Either via the charts authentik.secret or env var
AUTHENTIK_SECRET_KEY. For reference, here are all the env vars I define, maybe it helps: https://github.com/SquaredPotato/home-ops/blob/main/kubernetes%2Fapps%2Fsecurity%2Fauthentik%2Fapp%2Fsecret.sops.yamlHelmrelease is located in the same folder as you might’ve guessed :)
curled@lemmy.dbzer0.comto
Selfhosted@lemmy.world•My thoughts shopping around for a wiki solutionEnglish
2·2 months agoI’ve been using Outline for a while now. It has access control, external login (oidc, LDAP, GitHub, etc), a markdown compatible editor, plenty of integrations and is open source.
It’s fairly new and has some annoying bugs like not being able to resize mermaid diagrams, but for basic text articles it’s perfect.
To add on to your comment, and I’ve said this before, but specifically for military equipment, the terminology is military spec/milspec. The stuff labeled “military grade” is 100% bs.
Military spec can mean a ton of different things depending on the equipment. For example, for electronics it often means being in a blast, water and dust proof enclosure, and capable of withstanding rather impressive amounts of outside interference and temperatures.
This argument about lowest bidders everyone keeps coming back to is true, but the end product will still be of considerably higher quality than what you’re going to get as a normal consumer.
Because this equipment is often under tight import/export restrictions, getting your hands on it isn’t easy. Older gear can be bought at surplus stores, and maybe some things are easier to get in the US, but in general the good stuff won’t be for sale until it no longer hold value to the military that bought it.
/rant