Another busy week in the Scholars’ Lab R&D offices. If you have anything to contribute, remember, pull requests are welcome!
Rails 3.1 Template
The entire group has been working with Rails a bit more the past couple of weeks (we have lots of experience in the group with Python and PHP), and there were some humorous responses when I asked their thoughts on rails and the new asset pipeline:
“I like it a lot more than I used too…” – Jeremy Boggs
“The asset pipeline is easy enough to override…” – Eric Rochester
“Meh…” – David McClure
Eric Rochester reworked his blog in Octopress, a Jekyll framework for blogging (0b331a9). No more database overhead, just straight up HTML goodness! If you feel WordPress is overkill for your needs, and love markdown (or other minimalist markups), you should definitely check this technique out.
Eric Rochester found a bug in the Chef when using httpd on CentOS 6 (pull request). This update changes the default pid file for the httpd daemon and updates the Apache configuration to appropriately assign the pid as expected. There is really nothing worse than a stale pid file that stalls a daemon.
David McClure is getting closer to finishing a major refactor of the Neatline Maps plugin for Omeka, which makes is possible to display .tiff files hosted in GeoServer with a “slippy” map courtesy of OpenLayers. The current maps branch of the plugin has quite a number of UX improvements that ease the building of composite maps from of a number of files and associate them with Omeka items.
The Mind is a Metaphor
Wayne Graham has started the work of migrating a Rails 2 application to Rails 3 using upgrade plugins and rake tasks. Not only is this application upgrading frameworks, but also is being upgraded to run on Ruby 1.9. As support for Ruby 1.8.7 will reach its EOL, with normal maintenance until June 2012 and security fixes until June 2013. After spending some time grinding on this, enough has changed that I’m going to try a new tack and merge models and controllers into a blank project because of the difference in how rails sets itself up depending on if 1.9 or 1.8 is used to initialize the project.
We are attempting to standardize our git workflow to make a bit more sense and be “safer.” After reading the great piece by Vincent Driessen (“A successful Git branching model” pdf), we’ve begun utilizing gitflow. Essentially it breaks down to a master branch (the release), a develop branch (your next version), release versions (archive of past releases). You then create local “feature” branches that you merge in to the develop branch, merging up the tree as needed. I personally am digging the fact that to merge my local branches I no longer have to type:
git co develop git merge --no-ff mybranch git branch -d mybranch git push origin develop
There are only two lines now:
git flow feature finish mybranch git push origin develop