ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
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
Recovering from a Failed NetBox Upgrade When a NetBox upgrade fails during the migration phase, the database may be left in a partially updated state. Administrators must decide how to recover without corrupting existing data. Two Documented Approaches Restore a pre‑upgrade database backup – revert the entire database to a known good snapshot and roll back t
netlify
pm2