Skip to content

Default bundle cannot fully install at the default --body-limit (chat app is 13.6MB vs 10MB cap) #559

Description

@melvincarvalho

Problem

A bare first-run install of the default bundle (12 apps) fails on 2 of 12 apps with the out-of-the-box --body-limit (10MB):

  • solid-chat/app=chat — repo is 13.6MB (GitHub API size), pack exceeds the cap
  • JavaScriptSolidServer/git — same failure signature
✗ chat: push failed
  error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413
  send-pack: unexpected disconnect while reading sideband packet

Reproduced on jss 0.0.207 against a fresh single-user pod (--git --idp --single-user). With --body-limit 200MB the apps' content does land and serve (with separate rough edges — see companion issues).

This means the curated first-run experience ships apps that the default server config rejects.

Options

  1. Raise the default bodyLimit (e.g. 50MB) — the help text already frames raising it for git push; localhost single-user pods are the common case
  2. Keep 10MB but make jss install detect a 413 and print an actionable hint ("raise --body-limit / JSS_BODY_LIMIT")
  3. Trim or split the default bundle so every member installs under the default cap

Option 1 + the hint from option 2 seems the best UX.

Found while validating jspod#48 (install delegation) — jspod/jspod#78.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions