馃攳 Problem Description
Self-hosted Engram Cloud on the same machine over plain HTTP (:). Both cloud upgrade bootstrap --project and sync --cloud -- project refuse with cloud: bearer token requires an HTTPS remote URL- verified the check is scheme-only (loopback HTTP refused too, engram v2.0.0-rc.10). Workaround was terminating TLS via reverse proxy, but for same-host/loopbacl the token never leaves the machine.
馃挕 Proposed Solution
Request: allow loopback exemption or an explicit --insercure-local / env opt-in for bootstrap and sync.
馃摝 Affected Area
Sync (multi-instance)
馃攧 Alternatives Considered
Seperate note: sync is explicit-only today; an autosync path for enrolled projects would complete the story,
馃搸 Additional Context
No response
馃攳 Problem Description
Self-hosted Engram Cloud on the same machine over plain HTTP (:). Both cloud upgrade bootstrap --project and sync --cloud -- project refuse with cloud: bearer token requires an HTTPS remote URL- verified the check is scheme-only (loopback HTTP refused too, engram v2.0.0-rc.10). Workaround was terminating TLS via reverse proxy, but for same-host/loopbacl the token never leaves the machine.
馃挕 Proposed Solution
Request: allow loopback exemption or an explicit --insercure-local / env opt-in for bootstrap and sync.
馃摝 Affected Area
Sync (multi-instance)
馃攧 Alternatives Considered
Seperate note: sync is explicit-only today; an autosync path for enrolled projects would complete the story,
馃搸 Additional Context
No response