LAMP as a child of apache-php, in two content variants #1

Closed
opened 2026-09-27 18:01:27 -03:00 by marcos-mendez · 0 comments
marcos-mendez commented 2026-09-27 18:01:27 -03:00 (Migrated from github.com)

This repository is still an untouched fork of the upstream recipe. Everything
it needs now exists: apache-php is a layer on core with a green boot test,
and unit-mariadb is a fab unit that bt-layer records in the manifest and
subtracts by name.

Closes when:

  • lamp builds as a child of apache-php carrying the mariadb unit, and the
    manifest records that unit so a child of this layer does not re-run its conf
    script;
  • a second artifact builds without the database unit, for the stack whose
    database is elsewhere, and the names say which is which by content rather
    than by topology (handbook decision 0013);
  • the appliance's default page is the appliance's own and carries the mark,
    which is what every LAMP has had;
  • the boot test proves the stack rather than the ports: PHP executes on both
    80 and 443, the database answers with the declared secret in the variant
    that has one, and the variant without one refuses to start a local server
    rather than shipping an idle one;
  • keel diff is clean after first boot.

Equivalence against the monolithic build is the measure, the way the unit
extraction was measured: repeated control builds for the noise floor, the
package list identical, every differing file explained.

This repository is still an untouched fork of the upstream recipe. Everything it needs now exists: `apache-php` is a layer on core with a green boot test, and `unit-mariadb` is a fab unit that `bt-layer` records in the manifest and subtracts by name. Closes when: - `lamp` builds as a child of `apache-php` carrying the mariadb unit, and the manifest records that unit so a child of this layer does not re-run its conf script; - a second artifact builds without the database unit, for the stack whose database is elsewhere, and the names say which is which by content rather than by topology (handbook decision 0013); - the appliance's default page is the appliance's own and carries the mark, which is what every LAMP has had; - the boot test proves the stack rather than the ports: PHP executes on both 80 and 443, the database answers with the declared secret in the variant that has one, and the variant without one refuses to start a local server rather than shipping an idle one; - `keel diff` is clean after first boot. Equivalence against the monolithic build is the measure, the way the unit extraction was measured: repeated control builds for the noise floor, the package list identical, every differing file explained.
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Keel-Linux/keel-lamp#1
No description provided.