How to Rollback Migrations and Seeds in Render

When you deploy your application on Render, you often need to handle your database migrations and seeders automatically. By default, you might run a build command that migrates and seeds your database, but what happens when you need to undo those operations to reset your database or re-run them with new changes?

In this tutorial, you’ll learn how to rollback your Sequelize migrations and seeders on Render by modifying your build command, then restoring it once you’ve updated your data.

The Render Build Command

You likely have a package.json at the root of your repository that orchestrates the commands needed to build and migrate your backend code. Because your code is separated into backend and frontend folders, you need a convenient place (the root package.json) to run commands targeting each subdirectory.

A typical “build command” for your Express API might look like this:

npm install &&
npm run build &&
npm run sequelize --prefix backend db:migrate &&
npm run sequelize --prefix backend db:seed:all

• npm install – Installs dependencies in your root directory (and possibly subdirectories).
• npm run build – Could be building your frontend or bundling files.
• npm run sequelize --prefix backend db:migrate – Runs Sequelize migrations.
• npm run sequelize --prefix backend db:seed:all – Seeds the database with initial data.

Render executes these commands in sequence whenever you deploy.

Why Roll Back Migrations and Seeds?

Occasionally, you’ll need to roll back to a prior state:

• You changed a migration file and need to re-run it from scratch.
• You want to reset the data in your tables by undoing seeds.
• You’re experimenting with database schema tweaks.

Without rolling back, your changes might not take effect properly. Rolling back undoes everything (migrations and seeds) and gives you a clean slate.

Rolling Back in Render

To roll back and re-run migrations/seeders, you’ll update your build command in the Render dashboard. Replace your existing build command with something like:

npm install && 
npm run build && 
npm run sequelize --prefix backend db:seed:undo:all && 
npm run sequelize --prefix backend db:migrate:undo:all && 
npm run sequelize --prefix backend db:migrate && 
npm run sequelize --prefix backend db:seed:all

Let’s break it down:

• npm run sequelize --prefix backend db:seed:undo:all
  Undoes all seed files that have been run, wiping out that seeded data.
• npm run sequelize --prefix backend db:migrate:undo:all
  Rolls back all migrations, removing tables/columns introduced.
• npm run sequelize --prefix backend db:migrate
  Re-runs all migrations from the start, recreating the tables/columns with any updates you’ve made.
• npm run sequelize --prefix backend db:seed:all
  Reseeds the database with the updated seeds, if any.

After setting this new build command, trigger a redeployment in Render. It’ll run this sequence and effectively refresh your database.

Restoring Your Original Build Command

Once your database is in the desired state, switch the build command back to the original:

npm install &&
npm run build &&
npm run sequelize --prefix backend db:migrate &&
npm run sequelize --prefix backend db:seed:all

Why revert? Because it’s typically not ideal to blow away data and re-run migrations every time you push new code. We only do the rollback sequence when we need a fresh reset or to correct database schema changes.

Key Takeaways

• Render’s build command can run multiple shell commands in sequence, which is how we manage migrations and seeders in production.
• To reset your DB: Undo seeds, undo migrations, then re-run migrations and seeds. Update the build command accordingly and redeploy.
• Switch back to your standard build command once the reset is complete.

This workflow ensures you have the power to reinitialize your database whenever needed, without manually logging into the server or performing complicated steps. It’s all driven by a single build command that you can edit in the Render dashboard.