it's a feature, not a bug 🙂. secrets are intentionally kept out of ctx so that it's harder to shoot yourself in the foot by accidentally printing out all your secrets/serializing them somewhere. instead, secrets are stored in environment variables by default, and there's a helper function (stored in ctx) that can read them for you:

(defn my-handler [{:keys [biff/secret]}]
  (println (secret :biff.middleware/cookie-secret))
...

I.e. the values from config.edn are only ever used to provide the names of the corresponding env vars

the main reason I wanted to bake this into biff (instead of letting people just update their codebases if they switch away from env vars) is that the biff library code needs to read secrets, so I wanted it to have some kind of stable interface for doing so that wouldn't need to change

Thanks! I realised I was already doing it this way before and I just forgot 😅

haven't done it myself, but good luck 🙂 happy to help troubleshoot if you run into any problems

Hi @U0CKDV6DB, I setup full text search with biff using the following Update deps.edn add the following line.

com.xtdb/xtdb-lucene {:mvn/version "1.23.3"}

:biff.xtdb/opts 
  {:xtdb.lucene/lucene-store {}}

very cool, thanks!