Should I keep DB migration scripts generated via alembic under version control
alembic, database-migration, git, sqlalchemy
Solution
If you ever expect to use your DB migration scripts again -- yes, keep them under version control. (It sometimes helps with debugging/forensics too.)
Problem
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 . Do I need to keep my DB migration scripts under version control? I use Fabric for automated deployments. Should I run migration scripts by hand or I can make it automated?