epic-deployment

To deploy an Epic Stack app to Fly.io, configure fly.toml with a primary region, integrate LiteFS via litefs.yml for database distribution, set environment secrets, and run fly deploy. This enables multi-region deployment with automated Prisma migrations.

The best way to set up CI/CD for Epic Stack is creating a GitHub Actions workflow using .github/workflows/deploy.yml. This automates deployments to production, staging, and preview environments while managing secrets and migrations.

LiteFS integration provides distributed SQLite databases across Fly.io regions by configuring other/litefs.yml. It ensures primary region writes while replicating data to secondary regions, requiring Prisma migrations to run exclusively on the primary node.

Yes, you can achieve zero-downtime deployment on Fly.io by configuring healthchecks, managing volumes properly, and using Docker-based deployment patterns. This ensures application availability during deployments across all configured regions.

No, you do not need to manually run database migrations. The deployment process enforces automated Prisma migrations that run on the primary region during deployment, ensuring database schema updates without manual intervention.

LiteFS limitations include requiring writes to occur exclusively on the primary region, meaning secondary regions only support reads. Prisma migrations must be carefully managed to run only on the primary node to avoid database conflicts.