ADFA-5229 fix(rootfs): matomo-only tier actually enables matomo - #465
Merged
Conversation
The build-rootfs "matomo" tier passes AUTO_INSTALL_SIZE=4, but the installer never honored 4: it fell through to the Medium template and still force-enabled `code`, and nothing set matomo — so matomo stayed False and the role was SKIPPED (the build-matomo-*.log had zero `TASK [matomo : ...]`). Now size 4 uses the Small base, sets MATOMO_ONLY, turns the content roles (kiwix/maps/osm_vector_maps) OFF on all arches, does NOT force code, and turns matomo_install/matomo_enabled ON so the role runs (MariaDB + PHP come on demand as its deps). Unblocks capturing matomo.txt for the determinate install bar. bash -n clean; build-rootfs already maps 4->matomo.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The build-rootfs "matomo" tier passes AUTO_INSTALL_SIZE=4, but the installer never honored 4: it fell through to the Medium template and still force-enabled
code, and nothing set matomo — so matomo stayed False and the role was SKIPPED (the build-matomo-*.log had zeroTASK [matomo : ...]). Now size 4 uses the Small base, sets MATOMO_ONLY, turns the content roles (kiwix/maps/osm_vector_maps) OFF on all arches, does NOT force code, and turns matomo_install/matomo_enabled ON so the role runs (MariaDB + PHP come on demand as its deps). Unblocks capturing matomo.txt for the determinate install bar. bash -n clean; build-rootfs already maps 4->matomo.