I’ve had my head down in a large Bricolage CMS project over the last few weeks (well, that and some packing), so it was time that I came up for some air and some technical blogging. First exciting bit of news to report is David Wheeler’s announcement about the released of Bricolage 1.11.3 last week. This is the first (and hopefully last!) beta toward the release of Bricolage 2.0. There is a lot of shiny-new fun in this release, so you should give it a try if you’re so inclined.
The next bit of fun is also Bricolage related. One of the aspects of working with the Bricolage CMS that I find most enjoyable is that it is an entirely "back office" workflow and publishing system. That means that Bricolage usually runs on an entirely separate server from the "front-end" Web server, i.e., the server that delivers content to your site’s visitors.
There are several benefits of such a "back office" system, but — by far — my current favorite is the ability to take the whole damn thing with me on my travels: a complete working copy that I can continue to develop on while offline and without Internet access. This happens to be particularly handy when working from the road in South America.
And when I’m finished with my changes to various Elements and Templates, I simply run
bric_dev_sync and let my offline copy sync its changes to the live copy that the rest of the development team is working with.
The other unique Bricolage feature that I was pleased to finally get a chance to use is
make clone. Running
make clone creates an archive of your current Bricolage installation that can be easily installed on another server. With the archive in hand, I was able to simply run
make install on my laptop and, with relatively few headaches, soon had a perfect clone of the existing Bricolage instance running locally: elements, templates, content and media documents — well, er, everything.
Sure, none of this is exclusive to Bricolage, but it sure is makes the "digital nomad" life a bit easier. After all, isn’t that was Perl is all about?