ci+docs: nginx matrix job and Horde install walkthrough - #19
Merged
Conversation
… with hardcoded SCRIPT_FILENAME
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
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.
Summary
Some loosely-coupled improvements that all help automating and documenting initial installation of a new horde setup.
See also #11
CI matrix over apache2 and nginx.
install-integration.ymlnow runs the same install lane twice: once withapache2, once withnginx. Shared steps live once; per-webserver steps gate onmatrix.webserver.fail-fast: falseso a failure in one flavor doesn't hide a pass in the other.doc/INSTALL_HORDE.md. Human-readable walkthrough of the same flow the CI automates, structured so future pivots (nginx/apache2 today; mysql/mariadb/postgresql later; PHP variant later) slot into a matrix of small recipe sections without disturbing the main description flow.
Doc tree cleanup. The nested
doc/Horde/Hordectl/was a PEAR-era artifactThe matrix strategy with
if: matrix.webserver == '<flavor>'on the per-flavor steps was the smallest primitive that keeps shared code in one place while letting each branch express its own webserver-configuration idiom.