Skip to content

docs: fix local Typesense connection settings - #243

Merged
kthoms merged 1 commit into
operaton:mainfrom
pralav-25:docs/typesense-connection-setup
Nov 18, 2026
Merged

kthoms merged 1 commit into
operaton:mainfrom
pralav-25:docs/typesense-connection-setup

Conversation

@pralav-25

Copy link
Copy Markdown
Contributor

Following the local Typesense setup currently leaves TYPESENSE_PATH unset, so Docusaurus retains the production /typesense prefix when connecting to the Docker service at localhost:8108. That service is exposed directly at the root path.

Add the empty TYPESENSE_PATH= override to the local .env example and explain it. Align the production description and documented defaults with the existing HTTPS reverse-proxy configuration in docusaurus.config.ts.

Validation: npm run typecheck, npm run build, and git diff --check passed. The build reports existing broken-link and anchor warnings outside this README change. Tests were not added or run, per the account owner's instruction. No Docker service or live Typesense instance was started.

Prepared with Codex assistance.

@kthoms kthoms left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM; thank you for this doc fix!

@kthoms
kthoms merged commit 430e2ce into operaton:main Nov 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants