Teaching Laravel
05 Oct 2013I love to learn from other developers and share my knowledge. At work recently I needed to explain the Laravel 4 workflow. There are a variety of ways to go about this, and I thought about the pros and cons:
I love to learn from other developers and share my knowledge. At work recently I needed to explain the Laravel 4 workflow. There are a variety of ways to go about this, and I thought about the pros and cons:
It’s been a strange journey into the annals of Vim, but I’m now pretty comfortable using Vim as a PHP IDE. How did I get here?
I ran into a situation recently where I had multiple CodeIgniter apps which depended on the same config values. No problem, right? Just use a common third_party folder. That would work, except they were on different servers! My solution was to echo the config as JSON in one place, grab the JSON in other apps and load them as config values. Now you can do the same!
I ran into a nasty bug recently that was totally unexpected. I had a form that needed to be submitted to multiple possible locations such as submit item and save draft. I am trying to chill on JQuery overuse lately so I Googled a solution for this. Turns out I’m in luck! You can have multiple submit buttons with the same name but different values. Whichever one you click will be submitted, while the other won’t. Yay!
So I thought.
I recently got bit by the Sparks bug again. If you don’t know, Sparks is like CodeIgniter’s version of Ruby Gems. It’s a command-line-based package manager that lets you install stuff for CodeIgniter quickly and keep it up-to-date. It’s a great idea and I want to port my libraries over to this system.
So I thought I’d try to get Kenji’s CIUnit working with Sparks. His wiki says to just change one line in MY_Loader.php (which is created by Sparks) and you’re good to go. I found this to not be the case, so I did a little digging. Here’s what you need to do to get them to play nice together.