feat: bump jss to 0.0.195 and enable --git by default#27
Merged
Conversation
JSS 0.0.195 (JavaScriptSolidServer/JavaScriptSolidServer#466) adds auto-init on first push, which closes the last gap that prevented the git HTTP backend from being useful out of the box. This PR turns on JSS's git backend by default in jspod, so every fresh `npx jspod` produces a pod that is also a real git remote: - `git clone http://localhost:5444/public/apps/<name>` for any public-read path - `git push http://localhost:5444/public/apps/<name>` for any owner-write path (auto-creates the bare repo on first push) - `git pull` to stay current Implementation: - package.json: bump javascript-solid-server from ^0.0.194 to ^0.0.195 - options.git defaults true; new --no-git CLI flag for opt-out (matches existing --no-auth / --no-open shape) - --git or --no-git is always passed explicitly to JSS so the spawn intent is unambiguous regardless of JSS's own default - docs.html grows a "Git remote" section explaining clone / push / auth ergonomics with a link to the upstream Known follow-up (out of scope here): git CLI doesn't speak DPoP natively, so push from the CLI today needs `git -c http.extraHeader="Authorization: DPoP <token>"`. Worth a dedicated jspod helper script + dedicated doc; tracked separately. Refs #1 #26
Merged
melvincarvalho
added a commit
that referenced
this pull request
May 16, 2026
Brings the JSS 0.0.195 dependency + --git enablement (PR #27) to users. After publish, npx jspod produces a working pod that is also a real git remote, with auto-init on first push.
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.
Closes #26.
Summary
JSS 0.0.195 (upstream PR) adds auto-init on first push, which makes JSS's git HTTP backend genuinely useful out of the box. This PR enables it by default in jspod.
After this lands:
git clone http://localhost:5444/public/apps/<name>for any public-read pathgit push http://localhost:5444/public/apps/<name>to any owner-write path — auto-creates the bare repo on first pushgit pullto stay currentThe pod is a real git remote.
Changes
package.json—javascript-solid-server: ^0.0.194 → ^0.0.195index.js—options.git: truedefault, new--no-gitCLI flag (matches--no-auth/--no-openshape), always passes--gitor--no-gitto JSS explicitly so the intent is unambiguousdocs.html— new "Git remote" section + TOC entry, with clone / push / auth-ergonomics example commandsSmoke test (local)
Git: enabled (clone/push support)✓GET /public/test-repo/info/refs?service=git-upload-pack(fetch on missing repo): 404 ✓ — fetches don't auto-initGET /public/test-repo/info/refs?service=git-receive-pack(push on missing repo, unauth): 401 ✓ — ACL preHandler gates Write--no-gitopt-out also wiredKnown follow-up
Git CLI doesn't speak DPoP natively, so
git pushfrom the CLI today needsgit -c http.extraHeader="Authorization: DPoP <token>". Worth a dedicated jspod credential helper + a doc on the push flow once we have a working signed-in token. Tracked separately.Refs #1 #25 #26