TEST REPOSITORY. This is a throwaway harness for validating the Satis-replacement pipeline before it goes live. The publisher is
ASUWebPlatforms/webspark-composer-test. Do not point production consumers here. The production repo will beASUWebPlatforms/composer-packages.
A static Composer repository
for ASU Webspark packages. Package artifacts are stored as GitHub Release
assets; the packages.json metadata is served from GitHub Pages. You can view
the current metadata at https://asuwebplatforms.github.io/composer-packages-test.
This is a custom repository registry of composer packages, similar to one generated by Satis,
but simpler and tailored for ASU Webspark. The packages.json file is generated by
scripts/merge-packages-json.sh from metadata derived directly from each package's
own composer.json at build time, and accumulated here (committed) on every publish.
Add the repository to your project's composer.json:
{
"repositories": [
{ "type": "composer", "url": "https://asuwebplatforms.github.io/composer-packages-test/" }
]
}Then require packages as normal:
composer require asuwebplatforms/asu_brand- The repository must remain public for unauthenticated
composer install. - Branch builds are published as the
dev-mainversion. Require them withcomposer require asuwebplatforms/asu_brand:dev-main. - Release builds are published as the version in
composer.json. Require them withcomposer require asuwebplatforms/asu_brand:1.0.0(or whatever the version is).
- A push/tag on
webspark-composer-testruns the publish workflow there. - Each package subdirectory is zipped and uploaded as a Release asset on this repo.
- The publish workflow fires a single
repository_dispatchcarrying the new versions' metadata. rebuild.ymlhere merges that metadata intopackages.json, commits it, and deploys to Pages.
packages.json— the accumulator of record (auto-generated; do not hand-edit).scripts/merge-packages-json.sh— merges new version records into it..github/workflows/rebuild.yml— rebuild + Pages deploy.