Skip to content

Recognize a local Ollama endpoint as configured in the setup wizard#275

Open
omatheusmesmo wants to merge 1 commit into
mainfrom
fix/console-setup-local-endpoint
Open

Recognize a local Ollama endpoint as configured in the setup wizard#275
omatheusmesmo wants to merge 1 commit into
mainfrom
fix/console-setup-local-endpoint

Conversation

@omatheusmesmo

Copy link
Copy Markdown
Owner

What

The first-run setup wizard nagged a working local install to "set up an LLM". SetupState.llmConfigured() treated the placeholder LLM_API_KEY=dummy that the ./run.sh local Ollama stack ships as unconfigured. Now a loopback or self-hosted (Ollama) primary base-url counts as configured even with a placeholder key.

How

  • Extract the URL check as a pure static isLocalEndpoint(String).
  • Unit test (cloud endpoints not local; Ollama / localhost / loopback local; blank/null not local).
  • Add the junit5 test dependency and the empty argLine property a plain-Java unit test needs under Java 25 (same pattern as composition-model).

Verification

mvn install -pl console/deployment -am -DskipTests (compile + extension-descriptor) and the unit test both pass.

SetupState.llmConfigured() treated the placeholder LLM_API_KEY=dummy that the ./run.sh local Ollama stack ships as unconfigured, so a working local install was nagged by the first-run setup banner. Detect a loopback or self-hosted (Ollama) primary base-url and count it as configured even with a placeholder key. Extract the URL check as a pure static and cover it with a unit test (adds junit5 + the empty argLine property the plain-Java unit test needs under Java 25).

Signed-off-by: Matheus Oliveira <matheus.6148@gmail.com>
@github-actions

Copy link
Copy Markdown
Contributor

🚀 Docs preview for 4c4ab09 is live:

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