jasonwitty
92ec6ea1be
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>
20 lines
682 B
YAML
20 lines
682 B
YAML
# Copy to secret.yaml (gitignored), set real values, and apply once:
|
|
# kubectl apply -f secret.yaml
|
|
# user-email / user-password are the login tududi creates on first start.
|
|
# session-secret signs session cookies -- generate with:
|
|
# openssl rand -hex 64
|
|
apiVersion: v1
|
|
kind: Secret
|
|
metadata:
|
|
name: tududi
|
|
namespace: tududi
|
|
type: Opaque
|
|
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
|