title: Using Alembic Migrations with multiple projects
body: <p>I have two Flask applications using Flask-Migrate and Alembic.</p>
  
  <p>There are three tables, with one table that is shared between the two Flask applications, and is represented by <code>shared_models.py</code></p>
  
  <p>I am running into the difficulty that the shared table gets stamped with one of the projects alembic_version, and then the other project complains about it, despite the <code>shared_models.py</code> file being identical.</p>
  
  <p>What is a good strategy for handling this kind of environment?</p>