Octopress is a static site generator based on Jekyll with some nice pre-configurations and customizations added. Jekyll is a Ruby project that is included as a gem by Octopress. The Jekyll project seems to have a small community around it, probably helped by the fact that it makes it easy to add GitHub project pages. Most of the recommendations I’ve seen for starting a Jekyll site recommend finding someone else’s project on GitHub and forking it so you don’t have to start from scratch. Octopress is designed to be forked and modified as the base for a site. It has a Rakefile with tasks designed to aid in initial configuration, page and post creation, and deployment. So it can be a time-saver when compared to cobbling together your own Jekyll-based site and workflow.

POW

The documents recommend installing something new to me, perhaps because I don’t do much with Ruby. It’s Pow, a web server based on Rack and built using Node. When you install Pow, it runs all the time and watches for a certain top-level domain. The default top-level domain is .dev. It’s really very simple. You symlink a directory that Pow can use with the name of the domain. I symlinked my modified Octopress to “infovore” in the ~/.pow directory and now http://infovore.dev is served out of that directory. Pretty nice. I don’t have to start up a server or remember what port to use. Also, it doesn’t really matter that it’s just a directory of static files. Pow serves static files out of a public directory in the directory it is looking at, which is exactly how Octopress is set up.

Jekyll Import From Drupal

In order to import my posts from my Drupal site, I had to do some reading on the Jekyll wiki to figure out how to import. The migration process wants to connect to your Drupal database. My database is on my Slicehost VPS. I considered doing what I used to do for development, export my production database and import that to a local MySQL database. But I figured it’s simpler just to connect directly to the remote server. Rather than use the MySQL installed with MAMP, I decided to install MySQL using Homebrew, then I installed the Sequel and MySQL Ruby gems as noted at the top of the Jekyll Drupal migrator file.

As a side note, I already had rvm (Ruby Version Manager) installed, so the gems were installed to my user-local config directory at ~/.rvm.

In order to connect to MySQL on the remote server using SSH, I needed to forward a local port to the remote port, using something like ssh -L 3306:localhost:3306 infovore.info. I was able to connect to the remote MySQL server and run a few queries to re-familiarize myself with the Drupal schema.

The current migration script is pretty basic and doesn’t get some of the metadata, such as tags. It also only creates a redirect page for the base “/node/{nodeId}” URLS, not for the rewritten “pretty” URLs. The current migration script also doesn’t get the markup format. I played around with both Textile and Markdown on the few posts I did on the original Drupal blog, and I wanted to pull them all out and use the correct file extension since Octopress/Jekyll can handle both Textile and Markdown.

The query went from this:

1
2
3
4
5
6
7
8
9

SELECT node.nid,
     node.title,
     node_revisions.body,
     node.created,
     node.status
FROM node,
   node_revisions
WHERE (node.type = 'blog' OR node.type = 'story')
    AND node.vid = node_revisions.vid

to this:

1
2
3
4
5
6
7
8
9
10
11
12

select node.nid,
     node.title,
     node_revisions.body,
     node.created,
     node.status,
     f.name as format,
     u.dst
from node
   join node_revisions on node.vid = node_revisions.vid
     join filter_formats f on node_revisions.format = f.format
     left join url_alias u on concat('node/', node.nid) = u.src
where (node.type = 'blog' OR node.type = 'story' OR node.type = 'article')

This required a bit of digging into the data to get the right structure. I also added another query to get the tags as I looped over each post. This could have taken quite a long time if I had many posts, but it would only be a one-time hit.

Once I had the data, I needed to change the YAML metadata output at the top of the posts. I changed the original migrator to output a published value since I had a few unpublished posts and the tags.

I also had to modify the location to save the files to since Octopress stores posts in a different location then the default Jekyll location.

I’m not saving my repo on GitHub, so I’m posting the modified file as a gist on GitHub. I added a Rake task to push to Amazon S3, but I’ll deal with that in a later post.

The platforms, languages, frameworks I looked at include:

• Google App Engine using either Python or Java
• A VPS running Java/Clojure or Python
• Java/Clojure on Amazon’s Elastic Beanstalk
• Heroku with Clojure
• CouchDB running on Iris Couch
• A static site built with something like Jekyll

I didn’t seriously consider the last option, building a static site. Though I did eventually develop a goal of using other services as much as possible in order to avoid doing the work myself. While it is educational and useful to know, doing the SysAdmin work associated with running Drupal on my own server is time consuming. You have to keep the server updated, Drupal itself, and any Drupal modules used. I often want to build things myself so they’re just the way I want them, but the extra time can take away from doing something more useful.

I’d gotten to the point where I was focusing on a CouchDB solution because I thought it might present an opportunity to try to use ClojureScript. It would take a while to build a site that way, so I reconsidered and thought perhaps start with an existing blog app/framework and eventually rebuild it on the data with my own app.

CouchDB is possibly the closest you can get to a static site that is still database-driven. If you use CouchDB design docs to serve a site, there’s hopefully not much processing going on to generate the page. You would want to have the generated pages cached to avoid unnecessary load on what is nearly a static site since personal blogs tend not to be updated that frequently. In some ways it’s not a far step from a cached CouchDB site that isn’t updated frequently to just building a static site generated from files on your computer. One more nice thing about CouchDB is you can make your changes on your local database and send them to your production site using replication. That also makes your local database a good back-up of the production site.

I am anxious to get this blog going again so I can try out some HTML 5 and some aspects of the public web that I don’t get a chance to deal with at my job. This anxiousness kept me thinking what is the quickest thing I can build. Then last week I saw Werner Vogels’ post on moving his blog to a static site hosted on S3 and generated from files using Jekyll. I’d considered this before, but hadn’t looked into it much. The article prompted me to search some for static site generators. That post and its comments listed a few alternatives. Ruby had three good ones. But what finally pushed me one direction was finding Octopress. It bundles several features on top of Jekyll that made me decide to try it.

Octopress already has a theme, so I can just use its for a while. It has a few Jekyll plugins integrated. It uses SASS to generate the CSS. It seemed like a good place to get started quickly.

I cloned the GitHub repo and had test site running on my laptop without much effort or time, so without much thought about it, really, I just started the process of preparing for the move. I’ll get into the move from Drupal in a future post.

If you’re into old-time music, check out this station on Sunday mornings. Or if you’re in New York, you can tune in your radio to 89.9 FM. I don’t think it’s a very strong signal, so you may have a problem picking it up from any distance away.

http://www.columbia.edu/cu/wkcr/

The article, Think Small, mostly focuses on vacation homes. Vacation homes make great candidates for small houses (those under 750 square feet) since a larger house is going to require more upkeep. One thing you don’t want in a vacation or weekend house is doing upkeep on the house rather than enjoying yourself.

Small houses also make the land more important in comparison to the house. If you are in a small house, more time will be spent outside. And the greater tightness of the house makes the landscape all that much more important.

I have read articles about some of the small houses before, but I’m not sure where. I know I’ve read about smallish houses in Dwell. Dwell has had several articles about pre-manufactured housing, and small houses and pre-manufactured houses can easily go hand-in-hand.

I also saw a posting on Kevin Kelly’s Cool Tools site about Tiny Houses, but this isn’t what I was thinking of. It was probably in a long-gone magazine.

Here are some of the sites mentioned in the article.

• Alchemy Architects who make the weeHouse is based in Minnesota.
• BlueSky Mod is out of Toronto.
• Cavco Industries sells barebones cabins
• Tumbleweed Tiny House Company sells several different models, though some are plans only, not manufactured. They also sell tiny houses on wheels that can be moved. They have the greatest focus on tiny houses as they don’t sell larger models unlike some of the other manufacturers.
• Cusato Cottages created the Katrina Cottage for victims of Hurricane Katrina. Currently the cottages are only available in Missippi and Louisiana, but they’ll be selling the houses as kits through Lowe’s some time in spring 2007.
• Tiny Book of Tiny Houses book from the Cool Tools site. The author wrote other books on tiny houses, Tiny Houses: or How to Get Away From It All and A Little House of My Own: 47 Grand Designs for 47 Tiny Houses. I haven’t read any of these books, but I’ll be looking at them soon and may add them to my already hefty book collection.
  ]]> 2007-01-31T00:00:00-05:00 http://www.infovore.info/blog/2007/01/31/color-plastic-displays-will-lead-to-better-ebooks-soon New Scientist printed an article this week on new displays that put transistors on plastic, enabling flexible displays. I keep thinking–hoping–that the days of eBooks will soon be here. Maybe these displays will hasten their arrival. http://www.newscientisttech.com/channel/tech/mg19325886.000-goodbye-wires-and-silicon-hello-plastic-chips.html

  I hope the publishers are getting ready for this. Luckily for them I think their very analog, atom-based technology doesn’t lend itself well to pirating. Though that could be to their detriment as people continue to move to free content on the web. Granted there is much that can only be gotten in books, but those who release their books for free or cheap may gain a leg up in the new world where cheap, light, flexible eBooks are available.

  There’s still talk of a flat fee for all downloaded and shared music. Imagine a world where one could pay a flat fee for all the books you could read. Without getting into the mechanics of how something like that would work, just think about how everyone being able to access any book they want at any time would affect the knowledge circulating in the world. How nice it would be if that knowledge locked away in those analog books could circulate with the words on the web.

  Just before I finished this article, I found out about an article about Google’s book project in this week’s New Yorker, Google’s Moon Shot. I’m not sure if Google’s effort is going to be the path to ubiquitous eBooks, but it can’t hurt. Unless, as the article says, the law suits against Google, which will most likely be settled out of court, set up a huge financial barrier for other entrants to the arena. I can’t imagine anyone wants a monopoly set up in front of a huge pool of knowledge. If the music industry moves to some sort of common pool of money that gets (hopefully) equitably distributed, perhaps other industries will realize they can make money in an at least semi-free business model.

  And if the various industries don’t see the value, perhaps some of the individual actors within the industries will move and either lead the others into the future, or create an entirely new industry built on the skeletons of the old industry.

  ]]> 2006-11-13T00:00:00-05:00 http://www.infovore.info/blog/2006/11/13/possibly-the-worlds-oldest-man-died-recently Going through an old Economist today I read an obituary for possibly the world’s oldest man–Benito Martínez Abrogán. Some interesting things to note from the obituary:
  • He lived in Cuba most of his life, though he moved there from Haiti around 1925.
  • Cubans longevity matches that of Americans despite underspending the US in healthcare by US$5,460 per person.
  • He had no car, walking, biking, and taking the bus to go everywhere.
  • Food is rationed in Cuba, so he grew his own food, most of which was starchy cassava and sweet potatoes cooked in pork fat.
  • He never married.
  • He smoked till he was 108.
  • He never saw a doctor till he was 115.

  Apparently Cuba has quite a few centenarians, some 2,721 out of 11.2 million people. I don’t know how that compares to the US.

  There was an article in the New York Times recently about the effects of calorie restriction on aging. Mice fed a calorie-restricted diet with adequate nutrition (often shortened to CRAN) lived longer and had better health and were more active as they got older. Might the effects of calorie restriction have something to do with the general health of people in Cuba? I wonder if there are any other places to test the effects of this? Cuba and North Korea are two of the only places I can think of where there’s generally not as much food available as many would prefer, but aren’t suffering many of the problems of other poor countries, such as those in sub-Saharan Africa. Unfortunately, North Korea is so closed there’s no way to know what the general health of the people is like. But once North Korea opens up, as I’m sure it will one day, it will be an interesting place to study the effects of long-term calorie-restriction among a large population.

  Are the only places where people experience less available food and the people remain in generally good health going to be those where the modern conveniences are not as readily available? The cheap food from modern food processors are making their way to poorer countries as their rising obesity rates may be evidence of.

  Are the more advanced countries seeing a decreasing marginal return for the money spent on healthcare? Is it possible there might be better ways to spend the money than on ever more drugs to attack erectile dysfunction?

  Several questions raised by his obituary. But as a final note, I hope I can manage to be as healthy and active as I get older as Benito was.

  Health, Longevity

  Technorati Tags: Health, Longevity

  ]]> 2006-11-13T00:00:00-05:00 http://www.infovore.info/blog/2006/11/13/oriana-fallaci I only recently heard of Oriana Fallaci, which seems to be a massive misfortune on my part. I didn’t know anything about her until her death this past September. Another obituary I was reading in an old copy of the Economist [1] provoked some interest such that now I’m going to have to read one of her books. I’m going to start with her last one, The Force of Reason, though I’ll read the few stories of hers that I can find online, currently just through Wikipedia.

  [1] The Economist seems to now offer the same sort of service as Salon, where you watch an ad to get access to their content, so the link should be accessible.

  ]]> 2006-11-12T00:00:00-05:00 http://www.infovore.info/blog/2006/11/12/setting-up-ecto-for-drupal-5-0 After a lot of messing around with various settings in Drupal 5.0 I found that in order to edit your site with an external client such as Ecto or docs.google.com you have to turn on the blog entry content type and then give the user access to “edit own blog”. I guess I hadn’t tried to connect without having the blog module turned on even though the blogapi module lets you access other content types.

  I currently use a custom blog content type, which I could continue to use, but I noticed something once I turned on the blog module. I pull in feeds for my del.icio.us tags and Google Reader starred items, and now there’s a small link next to each feed item that lets you click on that to start a blog entry using that item’s information. I just checked it out, and I don’t know how useful it will be since it uses the existing item’s title as the new blog entries title and the body of the entry becomes the link to the item. It might turn out to be useful in some way though, so I’ll switch to using the blog entry content type and keep using the /articles path for the blog entries.

  ]]> 2006-11-01T00:00:00-05:00 http://www.infovore.info/blog/2006/11/01/problems-with-drupal-5-0-beta I thought I’d throw my notes in here as I find problems.

  I’m using Drupal 5.0 Beta 1, PHP 5.1.4, FreeBSD, MySQL 4.1.16.

  • The site name and tag are repeating for users that are logged in. It seems to be OK for anonymous users.
  • The Minnelli layout is slightly too wide for my screen and I get a horizontal scroll bar for the authenticated users since I have content in the left and right sidebars
  • This probably isn’t a Minnelli theme issue, but two blocks I created from my del.icio.us feed and Google Reader feed are not showing up for the anonymous user. It doesn’t seem to be turned off for any users.

  Several of the modules don’t seem to have been updated for 5.0 yet. Three I looked at that aren’t ready yet are CAPTCHA, Textile, and Text Image. I’m not really turning on comments yet, so none of those are a huge problem. I did download and install Scheduler, but I don’t see it available here even though I enabled it.

  Updated:Another problem: When I saved this article I got a bunch of errors related to the taxonomy module, such as warning: Illegal offset type in isset or empty in /users/home/stantont/web/public/modules/taxonomy/taxonomy.module on line 1087.

  Six error messages in all, all pointing to line numbers 1087, 1088, and 1091.

  ]]> 2006-10-31T00:00:00-05:00 http://www.infovore.info/blog/2006/10/31/setting-up-drupal Tonight I decided to go ahead and install the 5.0 Beta 1 version of Drupal. I installed version 4.7.4 over the weekend, but hadn’t done anything with it yet. So when I noticed the 5.0 beta was out, I decided I might as well move to it. I looked at a sample install of the beta from a link at the Drupal.org site, and I liked the better admin menu layout. The admin menu in 4.7 is confusing as there are different menu items with the same name, though at different levels. The beta menu seems to be thought out better.

  I was going to use the default theme, Garland, but when I looked at it as the anonymous user, the right side collapsed, so I’ve switched to the fixed width layout. I had added a couple of blocks which pull in my del.icio.us and Google Reader feeds, but those aren’t showing up for the anonymous user, so I’ll have to figure out why that’s happening.

  I’d like to get Drupal’s Navigation menu to not appear for the anonymous user, but I’ve yet to figure out how to get that to happen. I don’t see an obvious option in Access Control, Menus, or Blocks. But I’m sure I’ll see it eventually.

  I think I’ll turn off the user login block as that really makes it look like a Drupal site, and I’ll be the only one using it. I’ll leave the logo and favicon up for a few days till I decide what to do about those. It would be nice if there was an option with a few other images available by default. I haven’t been looking at Drupal for long, but I found the Lullabot podcasts and consumed all of those over the last week and a half. It’s nice that there seems to be a good community around it. I don’t know if Drupal’s community would seem as nice by half without the Lullabot group’s podcast. Ruby on Rails podcast helps foster their sense of community, and their active bloging helps as well. I’ve been looking at Django over the last couple of months, and it’s a better place to start for a CMS-y site. The Rails CMS/blog engines seem interesting, but probably need to do a bit more growing first. Django seems pretty mature for what it does, but it needs a more active feeling to it. I like Ruby and Python better than PHP, but I can deal with it.

  The Rails-community seems larger, and thus has more blog-activity. If I was Django, I’d try to keep putting up more content on their weblog so it keeps the feeling that more is going on. Perhaps the mailing lists can help that feeling, but I often find a blog article more engaging than 30 random posts on a mailing list.

  I started looking at Drupal because I have a couple of friends who want to make their company’s site more dynamic and flexible. I could have recommended Django or even Mephisto to them, but Mephisto seems a bit green for them since it’s still under fairly active development. And either one would have required quite a bit of work from me to get something going for them. And then they would be left tied to me since I’d probably have to run their server for them, and finding more Django or Rails talent would be difficult at best. PHP talent is fairly widespread, though dealing with Drupal would probably take someone who is at least somewhat familiar with it to get any real work done. Drupal does give them more hosting options as well. It should be pretty much a drop-in as far as setting up the server, and pretty much everyone supports PHP. Drupal also lets them do a lot of the administration themselves, if necessary, with it’s extensive admin menu.

  The number of contributed modules available is simply staggering. I tentatively started using some of the modules I read about. The Lullabot podcast helped a lot in this area as they are always mentioning what the most essential contributed modules are.

  I’ll spend a bit of time tonight adding a few modules, even though they’re not officially sanctioned for the 5.0 Beta yet. I’ll be a bit…parsimonious with what I add.

  I’ve still got a lot to learn about Drupal, but I like the energy I’ve seen behind it thus far.

  ]]>