Wolf Noble

iirc jmooring has advocated for the use of renderString vs markdownify; but i suspect this to be an artifact caused by prettier

ideal configuration would involve multiple node configurations ... storage tier ... log ingestion ... metrics ingestion ... some environments may split stuff out into a logging stack, and a metrics...

Is there anything preventing this from being merged?

what would it take to get something like this merged in? seems like a good starting point to be able to address encryption-key validation requests?

> I'm having the exact same issue, this has also been reported on the forums https://forum.opnsense.org/index.php?topic=47483.0 OP of this forum thread here…. happy to help diagnose if anyone’s got ideas…....

what i noticed looking at the interaction between browser and opnsense is that on pages which display the proper content there are two requests made to search. one for the...

`[root@evey /home/wolfspyre]`# `opnsense-version` `OPNsense 25.7.a_569 (amd64)` `[root@evey /home/wolfspyre]`# [hw-probe -all -upload](https://bsd-hardware.info/?probe=367288b06d) `[root@atticus ~]`# `opnsense-version` `OPNsense 25.7.a_606 (amd64)` `[root@atticus ~]`# [hw-probe -all -upload](https://bsd-hardware.info/?probe=5c9659c4de) I was watching all `latest.log` files in /var/log,...

Updating to 25.7.a_674 did not impact the behavior. I see an additional ajax call from my browser to opnsense on the pages which DO display content, and I do NOT...

Can confirm this worked for me on 25.6.a_674: ```shell [root@atticus /var/log]# opnsense-version ;uptime; uname -a OPNsense 25.7.a_674 (amd64) 3:17AM up 2 days, 9:08, 10 users, load averages: 1.44, 0.89, 0.78...

I'm experiencing the same thing, but mine is occurring in my json index templates trying to parse .Summary still trying to pare down to a minimum reproducible set to see...