ballroom-flow-run-and-operate

Local development uses pnpm dev to run the environment. D1 database migrations are managed separately through specific Wrangler commands to update the document graph schema across development, staging, production, and e2e environments.

The deployment pipeline involves executing step-by-step Wrangler commands for environment configuration, applying D1 database migrations, and deploying artifacts. It manages releases across development, staging, production, and e2e environments.

D1 database migrations are managed through Wrangler commands to apply schema changes to the document graph. You must run these migrations as part of the deployment pipeline before releasing to staging or production environments.

Yes, this workflow requires access to the Weave Steps repository and associated tools like Wrangler and GitHub Actions. These tools are necessary to configure environments, run local development, and execute the deployment pipeline.

Screenshot generation for marketing materials is automated via a dedicated pipeline. Generated TypeScript files are regenerated by executing specific artifact commands to ensure type safety across the codebase.

Admin actions and secret rotation are performed through guided ops actions within the Wrangler environment. This includes executing template seeding and rotating secrets across development, staging, production, and e2e configurations.