Back to corpus
research noteexperiment writeup candidatescore 28
Deployment Guide
This guide covers deploying TrajectoryOS to production. We'll use **Fly.io** as the primary example, but principles apply to other platforms (AWS, Railway, etc.).
Full HTML reader
Read the full artifact
Extracted abstract or opening context
This guide covers deploying TrajectoryOS to production. We'll use **Fly.io** as the primary example, but principles apply to other platforms (AWS, Railway, etc.).
1. **Fly.io Account**: Sign up at https://fly.io 2. **flyctl CLI**: Install via `curl -L https://fly.io/install.sh | sh` 3. **Docker**: For building containers 4. **Environment Variables**: Prepare production secrets
Migrations run automatically via `docker-entrypoint.sh`, but you can also run manually:
Similar workflow: 1. Connect GitHub repo 2. Railway auto-detects Dockerfiles 3. Set environment variables 4. Deploy
More complex but highly scalable: 1. Push Docker images to ECR 2. Create ECS service definitions 3. Set up Application Load Balancer 4. Configure auto-scaling
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.