I agree with you, I kicked off this workflow implementation phase with a simple bash script to see what parts need special knowledge and are ugly and not standard and then pushed back to the team to fix them. Using a bash script to automate the development environment setup sounds good but I thought I might have missed something, hence the question.<p>Do you think this is a good way to automate the boring workflow:<p>* git clone project<p>* make virtualenv<p>* edit config file<p>* npm install<p>* bower install<p>* exectue gulp build task<p>* enable apache internal url for project<p>* restart apache<p>?