Skip to content
← Documentation Platform stack

Platform stack and runtime boundary

How ExtensionFlow is built on CodeIgniter 4, MySQL/MariaDB storage, CI migrations, public controllers and admin-only release workflows.

01

Framework

CodeIgniter 4 provides controllers, routing, validation, migrations, models and service wiring.

02

Storage

Release metadata lives in the database; release artifacts and documentation files are stored in writable storage.

03

Boundary

Public pages are read-only. Admin pages own mutation: releases, compatibility, docs references and incidents.

ExtensionFlow is a CodeIgniter 4 application. The public side presents documentation, downloads, changelog, roadmap and update XML, while the admin side manages release records, compatibility registries, documentation references and status events.

Runtime-слои

LayerResponsibilityExamples
Public controllersServe catalog, docs, changelog, roadmap, status and update XML.DocsController, ExtensionController, DownloadController.
Admin controllersManage releases, extension records, compatibility registries and documentation references.ReleasesController, VersionsController, ExtensionDocumentsController.
ServicesEncapsulate access policy, release files, compatibility and status calculations.PublicAccessService, ReleaseFileService, CompatibilityService.
Migrations/seedsMake fresh installs reproducible and document platform changes in the system changelog.Compatibility registry seeds, documentation reference seeds.

Why this belongs in architecture docs

Framework and runtime details are useful for platform maintainers, but they are not needed in product-specific extension guides. Keeping them in architecture docs prevents public product documentation from becoming an internal implementation manual.