@warksit, I believe so, but you need to restart your vm with the --provision field. There may be times at some of the places I consult where I'm not able to do that. Some companies have dev.example.com running along side their production example.com for multiple people and I just have to fit in the workflow. Many times our first languages are lost in translation. For example, I do some work in Montreal, primarily with french speaking network guys and my french is well... weak. So what I hear might not be what was said, and vice versa.
I'm not saying the world should work this way, but it seems laravel by convention uses artisan commands for all this generation, and logical that one might want to have this preliminary step.
Truthfully I have no idea why it hasn't been a part of the commands available, I would imagine that it makes sense for this to be part of the regular migration command set. But again I'm new to laravel, I've never deployed production servers with laravel and certainly haven't contributed to it, so there may be a really good reason why it's not part of the workflow. I'm just making sure it's part of MY workflow.
I've suffered enough lost time to simple typo's over the years that anything I CAN automate, I just do.