DocumentationMotionCommons · Developer preview

Deploying MotionCommons

Deployment planning

Understand the services, configuration and review needed to operate an installation.

Docs/Deploy and operate
Ask Claude

Deploying MotionCommons

Page Markdown

The complete guide, ready to copy or save as a Markdown file.

Download .md ↓

Current deployment scope

MotionCommons does not yet provide a turnkey production deployment. This guide describes the build boundary and proposed service topology. Local synthetic checks and selected hosted database components do not establish an operational clinical installation.

The current application supports local development. AWS hosting and general managed scientific compute remain target choices. Confirm the actual target, migration history and enabled components before deploying.

Service topology

ComponentResponsibilityTarget
WebStatic public documents and authenticated SPAProposed S3 / CloudFront
APICaller-scoped authorization and coordinationProposed ECS / Fargate
Database, Auth and private filesStudy boundaries, identity and storage policiesConfigured Supabase target
Scientific workersPinned isolated CPU/GPU analysisProposed AWS Batch; fixed local worker exists
Media and monitorLive transport and permission-based removalReviewed LiveKit Cloud and separate monitor

Build the web application

Use Node 24. The web build writes apps/web/build/client. Public routes, including documentation, are prerendered into readable HTML. Authenticated routes use __spa-fallback.html.

Configure hosting to serve real static documents first, serve the SPA fallback for application routes and proxy /api to the intended authorized backend. Preserve query strings and fragments. Do not rewrite missing static assets into successful HTML responses.

No production host or domain is configured by running the build. TLS, domain routing, environment-specific settings and operational supervision must be established for the chosen target.

sh
npm ci
npm run typecheck
npm run build

Configure services and migrations

  1. Verify the exact development or deployment target and its existing migration history.
  2. Configure matching public browser/API Supabase settings. Keep elevated worker credentials server-only.
  3. Review forward migrations and their prerequisites. Some execution and telehealth work remains local-only; do not blindly apply every migration to a hosted target.
  4. Validate anonymous denial, actual-role access, private storage and the complete synthetic workflow on the intended staging setup.

Live media is a separate boundary

Synthetic mode uses a loopback LiveKit server. Current clinical configuration only accepts a reviewed wss://*.livekit.cloud endpoint. A general self-hosted clinical media deployment is not supported by that configuration.

Supervise the dedicated admission monitor, alert on stale health and provider removal failures, and establish outage containment. Drain calls before rotating the media project or keys.

Before operational use

These are operator requirements. This documentation does not claim that those procedures or a clinical deployment have been validated.

  1. Establish service health checks, bounded logs without sensitive content, monitoring and incident ownership.
  2. Define backup, restore, retention, export and deletion procedures; exercise recovery in an isolated environment.
  3. Review dependency/runtime versions, capacity, network boundaries, secret rotation and a concrete rollback plan.
  4. Before clinical data, obtain responsible privacy/security review and applicable agreements for the exact projects and features in use.

Accessibility

Make every MotionCommons page comfortable for you. Settings apply on this browser.

Text size

Your training, at your pace.

Reading & movement
Audio support

Spoken audio is unavailable in this browser. All instructions remain available as text.

Read this page speaks up to 1,800 characters of visible page text. Embedded dashboards have their own Read dashboard button.