feat(cli): jss install --bundle <source> (Phase 6 of #464) - #486
Merged
Conversation
Apt-style meta-packages on top of the install atom. Bundles are JSON-LD ItemList docs naming app specs to install. Same auth, same target, same per-app status; composes with positional ad-hoc names. jss install --bundle ./media.jsonld jss install --bundle media # → solid-apps/bundles/main/media.jsonld jss install --bundle <org>/<repo> # → that repo's main/bundle.jsonld jss install --bundle https://example.com/.jsonld jss install --bundle media chrome vellum # bundle + ad-hoc Bundle items are bare strings (any Phase 1+2 spec) OR objects with required app:spec + optional app:label / app:description. The install path normalizes both forms and feeds them through the existing parseAppSpec + installOne machinery. Bundle header (name + description) prints once. Per-app failures report individually; continue-on-error; exit non-zero if any failed. Resolves to raw.githubusercontent.com for the URL shorthands so the fetch returns the raw JSON-LD body (not GitHub's HTML page wrapper). Verified end-to-end: - local-file bundle (./media.jsonld) → all items installed - absolute-path bundle (/tmp/...) → works - items as bare strings + items as objects + items with rename suffix - bundle + ad-hoc args composed - bare-name shorthand → correctly fetches solid-apps/bundles/main/<name>.jsonld - malformed JSON, missing items, invalid spec — clear errors, exit 1 Fixes #485
Merged
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.
Fixes #485. Phase 6 — apt-style meta-packages on top of the install atom.
What
Same auth, same target flags as bare install —
--pod/--user/--password/--nostr-privkeyall work identically.Bundle shape
JSON-LD
schema:ItemList(per the #464 comment):{ "@context": { "schema": "https://schema.org/", "app": "urn:jss:app:" }, "@type": "schema:ItemList", "schema:name": "Media stack", "schema:itemListElement": [ "playlist", "pdf", { "app:spec": "foo/bar=mybar", "app:label": "Custom name" } ] }Items are bare strings (any Phase 1+2 spec) or objects with
app:spec(required). The optionalapp:label/app:descriptionare for UI tooling that consumes bundles; the install path ignores them.Verified end-to-end
./media.jsonld) → all items installed/tmp/.../bundle.jsonld) → worksfoo/bar=mybar)solid-apps/bundles/main/<name>.jsonld(404s today because the repo doesn't exist yet — populating that is a follow-up data task, not a code issue)URL resolution detail
Uses
raw.githubusercontent.comfor the shorthand URLs so the fetch returns the raw JSON-LD body, not GitHub's HTML page wrapper.Out of scope (follow-ups)
<pod>/.installed.jsonldwritten by each install, restorable viajss install --restore <pod-url>for cross-server migrationsolid-apps/bundlesrepo — needed for the bare-name shorthand to actually serve content. Separate data task.