Documentation
Everything needed to run your own Lecture instance: what a host needs, how to start it, what can be configured, and how to keep it updated.
Lecture is pre-1.0
A working prototype, used for real university work, but not feature-frozen: commands, image names and configuration details below are provisional, and the public container image and downloads are not published yet. The license is also undecided — see the versions page for what exists today.
Quickstart
Start Lecture and its database with Docker Compose in ten minutes, from an example compose.yaml to your first opened document.
Requirements
Docker Engine with Compose v2, about 2 GB of RAM, sensible disk space, and PostgreSQL 17 — the database Lecture runs on.
Configuration
Choose the image, the port, the database connection and where your backups live — all through plain environment variables.
Updating
The safe update path: back up first, move one version at a time, and know how to get the previous one back.
Troubleshooting
First load seems endless, the app won't start, edits are not syncing, or data looks missing after a restart — start here.
How the pieces fit
A Lecture deployment is deliberately boring: an application container (the API, the sync server and the browser app it serves) plus a PostgreSQL container, connected by a Docker network. Your users' browsers do the heavy lifting — Lecture is a Blazor WebAssembly PWA — so the server stays small, and offline data lives on the devices, not on your host.
Questions not answered here? Write to hello@nilox.network — at this stage, every question shapes the documentation.