Standard Docker upgrade
AllCodex persists campaign lore, SQLite files, and vector indices in/srv/allcodex on your host machine. This allows you to update containers without data loss.
1. Pull the latest images
Pull the updated container tags from GitHub Packages:2. Recreate the containers
Recreate and start the services. Docker replaces containers that have new images:3. Clean up old images
Remove old, dangling Docker images to free up disk space:Upgrading database schema and migrations
AllCodex Core (SQLite)
Core applies schema migrations on startup. The Express server checks the SQLite schema, runs pending SQL scripts, and updates the database.AllKnower (PostgreSQL)
If you run AllKnower via Docker, the container entrypoint runs schema migrations (prisma migrate deploy) before launching the web server.
If you run a local development setup (Method 2), apply Prisma migrations after checking out the latest code:
Re-indexing vector embeddings (RAG)
If a new AllCodex release changes embedding models or the RAG schema (such as updating Qwen embeddings), re-index your LanceDB vector database:- Open the Portal Settings tab.
- Under the Search Status card, look for the Reindex RAG section.
- Click Reindex All Lore to queue a background job. AllKnower reads all notes tagged with
#lore, regenerates embeddings, and rebuilds the vector database. - Alternatively, click Wipe DB Lore & RAG to wipe the LanceDB and Prisma metadata backends.