docs: decision note 0047, one image per application #40

Merged

marcos-mendez merged 1 commit from docs/decision-0047-one-image-per-application into main

2026-10-02 10:26:13 -03:00

marcos-mendez commented

2026-10-02 10:25:54 -03:00

(Migrated from github.com)

The WordPress chain: Keel Core, Keel Web, Keel PHP, WordPress with a MariaDB overlay; no Apache (0023).
States per mode: local MariaDB in simple and cloud simple, installed but disabled in cloud advanced, where WordPress uses Keel MariaDB appliances on the mesh and wp-content replicates through Syncthing (0032).
Keel Cloud is in no application image (0046); at most the node side client.
Why: shared content addressed layers; two images per app would share about 90% of their bytes and double builds, tests and releases. Sizes measured and estimated are in the note.
Adds the row to docs/decisions/README.md.

Basis of Phase 4 (tracker#46). Not to be merged by the agent.

Records decision 0047, approved by the maintainer on 2026-10-02: an application appliance ships as one image (for example debian-13-keel-wordpress), and the installation mode chosen at first boot decides what runs. - The WordPress chain: Keel Core, Keel Web, Keel PHP, WordPress with a MariaDB overlay; no Apache (0023). - States per mode: local MariaDB in simple and cloud simple, installed but disabled in cloud advanced, where WordPress uses Keel MariaDB appliances on the mesh and wp-content replicates through Syncthing (0032). - Keel Cloud is in no application image (0046); at most the node side client. - Why: shared content addressed layers; two images per app would share about 90% of their bytes and double builds, tests and releases. Sizes measured and estimated are in the note. - Adds the row to docs/decisions/README.md. Basis of Phase 4 (tracker#46). Not to be merged by the agent.