Design Prisma schemas and manage SQLite migrations with LiteFS in Epic Stack projects.
npx skills add https://github.com/walbuc/iac-sorteios --skill epic-database-walbuc
Please help me install this Agent Skill. Skill: epic-database Source: https://github.com/walbuc/iac-sorteios/tree/main/docs/skills/epic-database Command: npx skills add https://github.com/walbuc/iac-sorteios --skill epic-database-walbuc
Prisma, SQLite, and LiteFS integration for Epic Stack requires coherent guidance on schema design, migrations, seeds, and deployment patterns to streamline database work across local and multi-region environments.
Initialize and configure a Prisma + SQLite + LiteFS database setup for a new Epic Stack project.
High-intent search queries and answers about installing and using this skill.
To configure Prisma with SQLite and LiteFS in an Epic Stack project, define your Prisma schema blocks, establish migration commands, and set up seed scripts. You must also specify LiteFS write-read separation requirements for local development and multi-region deployments.
LiteFS handles multi-region replication for SQLite by distributing the database file across Fly.io regions. You must implement write-read separation in your Prisma operations, routing writes to the primary region and reads to local LiteFS replicas to ensure data consistency.
Yes, you can use Prisma migrations and seeding with SQLite in a multi-region Fly.io deployment. The workflow involves creating migration files, applying them to the primary database, and running seed scripts to populate initial data across your LiteFS replicated environments.
The best way to design Prisma schemas for SQLite in the Epic Stack is to define models with proper relations and indexing strategies. This approach optimizes query performance and ensures your database structure aligns with LiteFS replication requirements.
Yes, you need to implement write-read separation for Prisma when using LiteFS. LiteFS replicates SQLite databases across multiple regions, so routing write operations to the primary node and reads to local replicas prevents conflicts and ensures data consistency.
A key limitation of using SQLite with LiteFS for multi-region deployments is the strict write-read separation requirement. Writes must route to a single primary region, meaning write latency depends on the distance from the primary, and automatic primary election is needed during regional failures.
M-KolaczDesign and manage Prisma-based SQLite databases with LiteFS in Epic Stack projects.
epicweb-devDesign, deploy, and maintain Prisma-based SQLite databases with LiteFS for Epic Stack applications.
vobaseIntegrate Better Auth authentication into TypeScript applications with SQLite, Prisma, or Drizzle.
mbdeatonManage Epic Stack databases with Prisma, SQLite, LiteFS migrations and optimization.
