Using the file-system for a cache backend on a production Magento site is just asking for your site to run slowly. But what about development? Should you use a file-system based cache there or not? Well, that is ultimately up to you, but you’ll be able to work faster if you develop on a stack with a fast cache backend. My personal favorite is currently Redis. Magento supports this out of the box in later versions of Magento 1 as well as in the developer betas of Magento 2.
Recently the crew over at Classy Llama decided to finally jump on board the OroCRM train and begin the process of implementing the software for our own internal use. Sometimes I’m known as the server dude internally, and that’s exactly how I come into play in this endeavor. The question always must be answered, where will we host it? In my neck o’ the woods we run our software on old-fashioned bare-metal servers, which does mean we have some older software than I’d like at times.
I live and breath Mac OS X on a daily basis, with a large portion of my work revolving around the command line using mostly tools which I’ve installed with brew. Bash completion has likely saved me days worth of time over the past decade or so. Little did I know, up until recently, however, that there is an official tap with completion scripts (in addition to the ones which come with individual recipes such as git) which can be installed for tools like docker, vagrant and grunt.