-
Ekklesia v0.2.4 — External Module Installation & Persistence
Pre-ReleaseCI / verify (push) Successful in 1m13sCI / infrastructure-smoke (push) Successful in 38sCI / package-release (push) Successful in 49sCI / image-build (push) Successful in 30sCI / migration-smoke (push) Successful in 2m13sCI / deploy-smoke (same-origin) (push) Successful in 47sCI / package-publication (push) Successful in 1m4sCI / deploy-smoke (split) (push) Successful in 2m23sZayin_Admin released this
2026-10-10 17:31:49 +00:00 | 0 commits to main since this releaseThis release completes the generic external-module installation path validated by the Signage integration.
Highlights- Supports installation and runtime use of real externally packaged Ekklesia modules.
- Persists installed module packages independently of the application container.
- Restores installed-module discovery and loading after process restart and container recreation.
- Preserves module lifecycle state, database data, and migration history across restarts and reinstall scenarios.
- Restores external-module integration coverage in CI.
- Validates module UI, runtime, migrations, lifecycle, and persistence against a real packaged module.
Integration validation
Ekklesia Signage was installed from its packaged artifact into generic Ekklesia and successfully validated through: - package verification and installation
- module migration application and idempotency
- discovery and runtime activation
- Dashboard UI loading
- module API operation
- display runtime and kiosk pairing in headless Chromium
- process restart
- API container recreation using persistent module and database volumes
- disable/re-enable
- remove/reinstall with preserved data and strict migration history
Core CI passed all 8 jobs for the final integration branch.
No production migrations are applied automatically; existing operator-controlled migration behavior remains unchanged.
Downloads