chore: remove vestigial Typesense vars from env examples#2555
Open
luthen-seas wants to merge 1 commit into
Open
chore: remove vestigial Typesense vars from env examples#2555luthen-seas wants to merge 1 commit into
luthen-seas wants to merge 1 commit into
Conversation
Search moved to community-scoped Postgres FTS in buzz-search; no compose service or code reads TYPESENSE_API_KEY/TYPESENSE_URL/TYPESENSE_PORT anymore (the benchmark harness sources its own environment). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
wpfleger96
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes
TYPESENSE_API_KEY/TYPESENSE_URL(and the header port line) from the root.env.example, andTYPESENSE_API_KEY/TYPESENSE_PORTfromdeploy/compose/.env.example.Why
Search moved to community-scoped Postgres FTS in
buzz-search; no compose file defines a Typesense service and nothing in the tree reads these variables anymore (thebenchmarks/harbor-buzz-orchestraharness sources its own environment at runtime). Leaving them in the templates suggests a service dependency that no longer exists.Testing
Config-template-only change. Verified with
grep -ri typesenseacross compose files, scripts, and crates: zero remaining consumers.🤖 Generated with Claude Code