Packaging & Upload

Packaging Upload

End-to-end flow

1. Ensure your implementations compile and pass local tests.
2. Run edge-connector package to create a .tgz bundle with a manifest.
3. Run edge-connector upload to send the bundle to the nara platform.
4. In the webapp, assign the new bundle version to one or more deployments.

Packaging

edge-connector package \
  --implementations ./custom-implementations \
  --out ./artifacts

Notes:

• If TypeScript is detected, the command will run pnpm build (unless --no-build is set).
• The resulting bundle name encodes organization ID and timestamp.
• The manifest includes a checksum so the runtime can detect updates.

Uploading

edge-connector upload \
  --file ./artifacts/edge-bundle-org-123.tgz \
  --api https://your-nara-webapp.example.com

If you omit --file, upload can package the implementations directory on the fly using the same logic as package.

Authentication:

• uses the token stored via edge-connector auth
• derives the organization ID from the token
• sends the bundle and metadata to the platform upload endpoint

After upload

Once the bundle is uploaded, the nara webapp exposes it as a selectable version for deployments. You can roll out gradually by attaching it to a test deployment first.