jason/homelab-k3s
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Point tududi AI assistant at the local Ollama
Validate and Deploy to K3s / validate (push) Successful in 20s
Details
Validate and Deploy to K3s / deploy (push) Successful in 27s
Details

Browse Source 
tududi speaks the OpenAI chat completions API for its daily brief and
task/project insights, so it can use the Ollama box directly instead of a
hosted provider -- nothing about the task list leaves the network.

LLM_API_KEY has to be set even though Ollama ignores it; without a key
the generation endpoints answer 503 and the UI shows a not-configured
state. It is a secret so the value can be swapped for a real one if the
provider ever changes.

gemma4:e4b was checked against the JSON-only replies these features parse
and answered correctly in about five seconds.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
jasonwitty
2026-08-12 14:01:32 -07:00
co-authored by Claude Opus 5
parent dde8b17fc4
commit 92ec6ea1be
2 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/tududi/secret.example.yaml
+4
View File
@@ -13,3 +13,7 @@ stringData:
user-email: you@example.com
user-password: CHANGE-ME
session-secret: CHANGE-ME
# The AI assistant requires a key to be set even when the provider ignores
# it (a local Ollama does). Any non-empty value works there; replace with a
# real key if you ever point LLM_BASE_URL at a paid provider.
llm-api-key: ollama