NOTE: This WeKan-Lite version has retro-look. Modern-look original WeKan is at https://wekan.fi and https://github.com/wekan/wekan .
Uses DOS filenames 8 characters, with extension 3 characters, like FILENAME.TXT
WeKan-Lite is a FreePascal HTTP server with an HTML board interface and a subset of the WeKan REST API. Its architecture draws on two companion prototypes:
wami/wekan.pas— single-file WeKan web prototype (routing + retro HTML surface).omi/public/server.pas— mature server (no-cookie/no-JS auth, SQLite-via-CLI, i18n).docs/contract.md,src/schema.sql,docs/goals.md,docs/webstack.md,docs/schema.md— the portable contract these target.
Keep shipped path components DOS 8.3-safe: names of at most eight characters,
extensions of at most three, letters/digits/hyphen/underscore, and one extension dot.
Host-only VCS/editor dotfiles are exceptions. Runtime paths, strict SQLite auxiliary names and offline migration are documented in docs/runtime.md. Build intermediates belong under
build/arch/<code>/ and collected binaries under build/bin/w<code>.exe, with platform
codes of at most seven characters. See TODO.md for implementation status.
The native embedded build includes public/i18n assets and private tenant/Designer SQL defaults. Fresh initialization and HTTP workflows are verified from a copied executable on linked/CLI SQLite without source or asset directories. Disk builds also need the SQL files or explicit path overrides. See embedded builds and SQL bootstrap; cross-target acceptance remains in TODO.
From the repository root, use Free Pascal with its FCL and SQLite units
and the system SQLite library. To use the SQLite command-line tool
instead, add -dWLDB_CLI and make sqlite3 available on PATH.
mkdir -p build/native
fpc -O3 -Xs -FUbuild/native -FEbuild/native -owelite src/wlhttp.lpr
WELITE_SHARED=0 WELITE_DATA="$PWD/build/data" WELITE_PORT=5500 ./build/native/weliteOpen http://localhost:5500/. Run the disk build from the repository root
so it can load the SQL, assets, and catalogs. Plain HTTP is the default.
The cross-build record gives target-specific compiler and
SQLite requirements.
- Native Linux linked and CLI SQLite builds run the HTTP and Chromium suites. Web sign-in and board navigation work with JavaScript disabled and first-party cookies blocked. Card titles open an HTML page with their descriptions and checklists, subtasks and attachment downloads. Board movement, selection actions and Designer use HTML forms.
- The REST API supports bearer-token login and board-scoped custom-field operations. On Linux, all 114 upstream REST cases pass on linked and CLI SQLite in shared mode. The REST browser cases run without JavaScript or cookies. See the upstream REST test runner.
- The FerretDB adapter opens existing shared SQLite stores and provisions new tenants in shared format when the SQLite backend supports it. Consult TODO.md for remaining interoperability gaps.
- The cross-build record distinguishes successful builds, emulated runtime checks and platform acceptance still to be tested. Chromium results cover Chromium. Amiga, MorphOS, and FreeDOS browser acceptance remains open.