In my previous post about Git workflows with WordPress, I suggested that you should put all files, including plugins and core files, under version controll. For example, Chris Coyer does this in his screencast about this subject. However, I don’t think it’s the best way to work in every possible situation.
Workflows and best practices are something that I am kind of obsessed about. What’s the best way to concatenate and minify scripts and stylesheets? To optimize images? To manage dependencies?
So you’ve read about this Git thing on Twitter or maybe listened to an annoying colleague who keeps talking about it. Perhaps you’ve come to the conclusion that Git is something good and you should probably use it.
I spend a lot of time these days trying to learn test driven development, TDD. I belive it was about a year and a half ago when I first came across this concept. Maybe not that surpriceingly, I was learning Ruby on Rails at the time. (TDD is a lot more common in the Ruby community.)
The typical scenario is that you are using MAMP (or WAMP) to create a local installation of your Laravel application. This will work just fine until it’s time to deploy your app to an production server.