I'm just wondering, having picked up another project that doesn't use Laravel that I'd like to move to using Laravel, is there any reason why you'd want to re-create the DB using Laravel migrations and if so, is there an existing package that will reverse engineer a DB into Laravel migration files ready to be run?
Thanks guys, so people use these then, rather than just working with the DB independently? It's interesting because I work a lot with a DBA who really is adverse to this kind of thing so I'm interested to learn the reasonings why it should or shouldn't be adopted from a wider stand point.