title: Sharing Eloquent Migrations with Team
body: <p>I am working with a couple of team members on a suite of web apps for our company. We have two projects that need to share a database. One project is public-facing, the other is for internal use only. We feel there has to be a better way to effectively share migrations. The apps are far too different to be separate branches of the same project. We have become frustrated with needing to compare Schema build information for simple database refreshes on our development server. There must be a better way. Please help!</p>
  
  <p>If needed, I will elaborate the reasons we choose to keep these projects separate and why we are sharing a database.</p>
  
  <p>Thank you.</p>