ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A practical guide to creating, running, and verifying database migrations in CakePHP 4.x using the built-in Phinx integration, with rollback procedures and team workflow rules.
Learn how to use Liquibase contexts to manage environment-specific database migrations using a single changelog without code duplication.
Context Hoppscotch self-hosted applies database schema changes through Prisma migrations tracked in the prisma/migrations directory. Prisma does not ship a built-in migrate rollback command, leaving administrators without a documented single-command path to revert a schema change safely. Constraints Reverting a migration currently requires either authoring a
We use Ballerina's persist feature to generate type-safe data-access clients and SQL migration scripts from a Ballerina data model, backed by a relational store (PostgreSQL in our case, with MySQL in some environments). Applying model changes forward works well, but the persist tooling does not appear to generate down-migrations or any automated rollback pat
Migration leadership and lock ownership In a Mattermost high-availability cluster running v8.x, the first node to start acquires a PostgreSQL advisory lock and executes pending database migrations while other nodes block on the same lock. The documentation states that only the leader runs migrations, but it does not specify what happens to the advisory lock
Goal Deploying a new application version that includes a database schema change requires that the rollback process also revert the migration. PM2’s pm2 deploy command can roll back application code, but it does not touch the database. Constraints and Uncertainty Rollback only reverts the last commit, leaving the database in the new state. A mismatch between
When designing a repeatable development environment for Entity Framework Core (version 8.0+), the choice of schema initialization affects how the database handles evolution and state. The goal is to establish a consistent baseline for developers and automated integration tests while minimizing startup overhead. Database.EnsureCreated() provides a fast, clean
When deploying schema changes on Railway, developers must choose between single-step migrations and the 'Expand and Contract' pattern. Since Railway does not natively guarantee transactional DDL across all database engines, a failed migration can leave the schema in an inconsistent, partially migrated state. Single-step migrations rely on manual 'down' metho
Goal Plan a zero‑downtime migration for a small application moving to Netlify, ensuring that static assets, preview environments, and database schema changes coexist without service interruption. Key Constraints & Uncertainties Atomic deploys swap in a fully built build only after successful completion, but they do not manage stateful database changes. S
cakephp
prisma
hoppscotch
ballerina
mattermost
pm2
entityframeworkcore
railway
netlify