[monkey](https://matrix.to/#/@monkey:chatbrainz.org): i imagine you're aware already, but BB seems to be pinning a *very* old elasticsearch version
2025-10-28 30107, 2025
julian45[m]
and although prod could be different, the postgres version seemingly indicated in the bb-site repo (12) has been EOL for almost a year
2025-10-28 30104, 2025
monkey[m]
Yes, the search upgrade is a big refactor project that I always find no bandwidth for. Will see if we can split it up with ansh to get it moving forward
2025-10-28 30151, 2025
monkey[m]
The postgres version is incorrect, it's on the same cluster as other DBs. I was just fixing that yesterday in the dockerfile
2025-10-28 30124, 2025
monkey[m]
(to be clear, fixing the utils version that is installed to match the cluster version [16])
2025-10-28 30100, 2025
monkey[m]
I'm noting down to update the PG version in docker compose files as well.
2025-10-28 30119, 2025
julian45[m]
<monkey[m]> "Yes, the search upgrade is a big..." <- gotcha, thanks for the response! fwiw if you want to stay on something elasticsearch-like, depending on your feelings on licensing, you could either go for a more recent elasticsearch version, or perhaps "opensearch" which forked from es a little while back
2025-10-28 30132, 2025
julian45[m]
both of which will have the option of a gui for viewing/querying/managing indices: kibana for es, "opensearch dashboards" (basically just kibana but aligns to opensearch branding/semantics) for opensearch
2025-10-28 30148, 2025
julian45[m]
es pros: the "original"^, faster dev cycle, arguably substantially easier to yeet data into especially in infra use cases... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/download/chatbrainz.org/uWiviFmWMdWDwppcOOukUhLD>)
