Should I keep DB migration scripts generated via alembic under version control

Question

I am using SQLAlchemy and PostgreSQL on my live site. For database migrations, I am using alembic. I have some questions regarding the best strategy to do this .

1. Do I need to keep my DB migration scripts under version control?

2. I use Fabric for automated deployments. Should I run migration scripts by hand or I can make it automated?

Answer 1

If you ever expect to use your DB migration scripts again -- yes, keep them under version control. (It sometimes helps with debugging/forensics too.)

Answer 2

I agree with Mark on version control: there's no reason not to include your migration scripts.

As for Fabric, I prefer to keep migrations out of it, or at least in a task that is not called implicitly by other tasks. That way errors can't be missed.