What’s up with the pictures?

Update

Read my latest post on my image header for how I ended up carrying out this idea.

People have been asking what the deal is with the images in my site header.

I’ve been experimenting with loading random background images from my collection using Drupal’s integrated jQuery tools.

I’ve been thinking about trying to work on having the images feed from a flickr stream, perhaps using the Drupal flickr module, yet be automatically sized/cropped for the site header. More on that if I get to it.

Many of the pictures are of people in my family, or shots I’ve taken around our home or Portland.

Praying to a New God: Ninkasi, The Sumerian Goddes of Fermentation

My new favorite beer is made by Ninkasi, in Eugene, Oregon.

They make an IPA that is simultaneously deliciously bitter and has all kinds of floral flavors that make each sip a trip to the Sumerian equivalent of Nirvana (An?).

They apparently brew in the Steelhead facility and haven’t managed to build much of a web presence yet:
http://ninkasibrewing.com/

So far, I’ve only found Ninkasi on tap, and at these Portland, OR establishments. Add a comment with other locations if you’ve found Ninkasi somewhere else…

 

Now Blogging with PHP 5/MySQL 5

Thanks to quick work by my host Liquidweb (thanks Siena!), this site is now delivered by the three fives: Drupal 5, PHP 5 and MySQL 5. Still waiting for Linux 5 and Apache 5 ;)

One of my goals here is to demonstrate/evaluate how this technology will operate on a forward-looking platform. Ever since Rasmus Lerdorf himself suggested dropping PHP 4 for the good of all at OSCMS 2007, I figure we better get ready for the future.

Check my blog recipe for platform details.

OSCMS 2007: Open Source Content Management Systems at Yahoo!

Recently returned from the Open Source Content Management Systems (OSCMS 2007) gathering held at the Yahoo! campus in Sunnyvale, CA.

Drupal was strongly represented at OSCMS, but also saw some Joomla, Plone and Alfresco presence.

As often, PHP maven Rasmus Lerdorf was in attendance, in this case, demonstrating the latest in security and performance considerations.

I found great value in the day-long seminar on Drupal/LAMP performance and scalability given by Dries Buytaert (Drupal), James Walker (Bryght), Jeremy Andrews (CivicSpace) and Matt Westgate (Lullabot), with a guest appearance by Robert Douglass (Lullabot). If anyone continues to have doubts about LAMP platform applications scaling to enterprise levels…they should have been in attendance to absorb the variety of solutions from hardware to network to architecture to database to code offered here. After this, I will no longer doubt that LAMP applications can be tailored to meet enterprise demands.

View the OSCMS Flickr stream

Drupal 6 Blog Recipe

LAMP Platform

Drupal Content Management System

Drupal Installation

  1. Procure a LAMP webserver environment similar to the one described above. Other platforms are possible (eg, LAPP, WAMP, WIMP, etc), but will not be discussed here. Read Drupal’s system requirements for more information.
  2. Follow the standard Drupal installation procedures.
  3. Once Drupal is installed, check your site’s system status (at http://yourdomain.tld/admin/reports/status) to make sure you have properly and completely installed Drupal. Fix any reported issues.

Drupal Configuration

  1. Complete the basic Drupal site configuration.
  2. For basic settings, I recommend using clean URLs. You might wait to enable caching and/or disabling on-screen error reporting until you are ready to make your site live.
  3. Enable the optional core modules listed below.
  4. Install and enable the theme listed below, choose another existing theme, or design your own Drupal theme (Framework is a good theme on which to base a new design).
  5. Install and enable the contributed modules listed below. Any specific installation issues will be noted under each module listing.
  6. Set up a cron task that will visit your Drupal site on a regular basis to do basic housekeeping tasks automatically (eg, rebuilding the search index).
  7. Establish an OpenID identity with a provider (eg, myopenid.com, myvidoop.com) and use it to log in to your Drupal site. (Note: I don’t recommend using Drupal’s root administrative user as your daily blogging identity, so make a new user for yourself with reduced privileges.)
  8. Start blogging!

Optional Core Modules

Ultimately, all these core modules are optional, but some provide basic functionality you won’t want to blog without.

  1. aggregator: Enables you to expose feeds (eg, RSS) from other sites on your site.
  2. blog: Blog enables multi-user blogging. If only one person will ever blog on your site, you don’t need the blog module. However, even though I may be the only blogger on xolotl.org, I’ve enabled blog to establish handy navigation to my blog, and other modules may add useful functionality directly to blog.
  3. blog api: Allows users to post content using applications that support XML-RPC blog APIs.
  4. comment: Enables you or other users to comment on your blog entries (or other content).
  5. contact: Provides general site contact form.
  6. database logging: Logs and records system events to the database.
  7. help: Provides online help for Drupal features.
  8. menu: Enables your site to have navigation menus.
  9. openid: Enables OpenID authentication. Note that I did some user login, login block, register and password form templating to override stock forms provided by Drupal and this OpenID module. My goal: allow only OpenID authentication.
  10. path: Enables you to make URLs on your site more human and search-engine friendly.
  11. php filter: Allows embedded PHP code/snippets to be evaluated.
  12. ping: Alerts other sites when your site has been updated via ping-o-matic.
  13. poll: Enables simple polling functionality. I’ll occasionally be asking my blog readers to vote on simple polls.
  14. search: Enables Drupal’s built-in content search functionality.
  15. statistics: Enables Drupal’s built-in usage statistics functionality.
  16. taxonomy: Enables you to categorize content with your own custom tags.
  17. update status: Checks the status of available updates for Drupal and your installed modules and themes.
  18. upload: Enables you to attach/upload files (eg, images, PDFs, etc) to content items.

Contributed Modules

Some of these contributed modules use additional required supporting modules where are not listed here.

  1. cck: Allows administrators to define new content types. I also use some custom CCK field type modules, that enable date, email, filefield, imagefield and link fields.
  2. flickrsync: Reads users’s Flickr photo streams, and turns into nodes.
  3. google analytics: Adds Google Analytics javascript tracking code to all your site’s pages.
  4. imagecache: Dynamic image manipulator and cache.
  5. mollom: Protects against comment and contact form spam.
  6. pathauto: Enables custom, automatically-generated URLs for pages.
  7. print: Enables printer-friendly, PDF and email versions of pages.
  8. service_links: Automatically adds Digg, del.icio.us, reddit, Technorati etc. links to content items.
  9. simplemenu: Creates a menu bar that is displayed at the top of every page.
  10. tagadelic: Tagadelic makes weighted tag clouds from your taxonomy terms. See the one in the column to the right.
  11. tinymce: Enables a WYSIWYG rich text editor.
  12. views: Create customized lists and queries from your database.

Theme

framework: I’m using a slightly modified version of the Framework theme by Andre Griffin. My modifications are only to default to OpenID authentication and some minor CSS style tweaks.