WeKnora: grounded answers, scoped memory and deliberate operations
Deploy WeKnora with a known image version, bounded services and a tested data plan
Separate standard Compose, Lite and development mode; understand cached images, migration risk and why full profiles are optional.
What you will learn
- Choose the deployment shape before adding services
- A new checkout does not replace an old container image
- Verify health, function and recovery independently
Before you start
- Basic HTTP and container concepts
- Understanding of documents, passages and model providers
Separate ingestion, retrieval, answer support and memory scope, then design an evidence-based acceptance exercise.
Key takeaways
- Core services and optional profiles have different resource costs.
- Pulling the selected image version matters when upgrading.
- Health checks do not replace functional and recovery tests.
Choose the deployment shape before adding services
The installation guide describes standard Compose with PostgreSQL-based storage and Redis, Lite with SQLite and in-memory coordination, and development mode with application processes on the host. It marks the desktop application as not officially released at this revision. Do not treat every listed packaging path as an equally mature release.
For standard Compose, begin with core services and add profiles only for a demonstrated need. The guide’s hardware starting point is an estimate, not a capacity guarantee for local inference, large scans or optional observability stacks. Size the chosen models and parsing workload separately.
A new checkout does not replace an old container image
Set the intended WEKNORA_VERSION in your reviewed configuration, pull matching images, and recreate the relevant services. The README explicitly warns that up alone can reuse cached images and leave the displayed UI version behind the downloaded release. A pinned source citation in this article does not pin your image tag or digest.
Create secrets and configuration in the deployment environment; never paste real values into an article or commit them. The documented frontend and backend ports are defaults, not proof that they are private. Bind or firewall the intended interfaces and keep the service internal until access controls are verified.
Verify health, function and recovery independently
A healthy backend is only the first gate. Check model connectivity, parse a synthetic document, retrieve the expected passage and inspect its answer citation. From a container, localhost refers to that container; the guide uses host.docker.internal for a host Ollama service, whose availability must be confirmed on the target platform.
Automatic database migration makes upgrades more than an image swap. Back up the database, stored files and required configuration, and test restoration before upgrading important data. Do not use volume-deleting shutdown or database-clean targets as routine troubleshooting. No deployment or recovery drill was executed here.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Choose standard, Lite or development mode deliberately.
- 2
Review secrets, image version and exposed ports.
- 3
Start core services and test a synthetic knowledge path.
- 4
Verify backup and restoration before a data migration.
Copy-ready example
docker compose ps
curl http://localhost:8080/healthFrequently asked questions
Why might the UI look unchanged after an upgrade?
The README warns that up alone can reuse cached images; verify the selected tag and pull result.
Should I enable the full profile first?
Only if those optional services are needed and their resource and security settings have been reviewed.
Sources
- WeKnora / README.mdSource checked 2026-09-14
- WeKnora / website-docs/01-getting-started/02-installation.mdSource checked 2026-09-14
- WeKnora / website-docs/01-getting-started/03-quickstart.mdSource checked 2026-09-14