Skip to content

fix(opencode): default to the compose llama-server port for the local route - #2980

Open
patil2001 wants to merge 1 commit into
Osmantic:mainfrom
patil2001:oc3-fix/opencode-linux-url-default-port
Open

fix(opencode): default to the compose llama-server port for the local route#2980
patil2001 wants to merge 1 commit into
Osmantic:mainfrom
patil2001:oc3-fix/opencode-linux-url-default-port

Conversation

@patil2001

Copy link
Copy Markdown
Contributor

Summary

The macOS fresh-install env generator wrote LLM_BACKEND=llama-server twice into the generated .env. Today both copies agree, but duplicate-key consumers (the shipped validator flags duplicate assignment as an error) treat the file as invalid, and editing one copy while leaving the other invites reader-dependent drift. The stray second write is removed.

AI Assistance

AI-assisted scan of the generator heredoc. The author reviewed the canonical-format contract and is responsible for the final diff.

Release Lane

  • Stable hotfix targeting release/2.6.x
  • Mainline change targeting main
  • Next-minor work targeting the next feature/minor release
  • Not sure; reviewer should help classify

Stable hotfix reason:

Not targeting the stable release branch directly.

Changed Surface

  • Docs only
  • Tests only
  • Dashboard UI
  • Installer
  • Core runtime
  • Dashboard API
  • CI workflows

Validation

  • bash -n ods/installers/macos/lib/env-generator.sh - passed.

… route

The non-lemonade, non-switchboard branch of the OpenCode config writer
defaulted the local llama-server URL to port 8080, but docker-compose.base.yml
exposes llama-server on OLLAMA_PORT (default 11434). With OLLAMA_PORT unset in
.env the generated opencode config pointed at a dead port.

Align the fallback with the compose default of 11434.
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.

1 participant