“Where are we going…and why are we in this hand basket?”
If you have an established blog and have readers who subscribe to your feed you’ll likely loose them when you migrate to WordPress and your RSS feed URL changes. WordPress feed look like http://www.mysite.com/blog/feed/ if you’re blog is at http://www.mysite.com/blog/. My previous blog software’s RSS feed url looked like http://www.mysite.com/blog/?wl_mode=rss2. I didn’t have too many subscribers, but there were a few and I didn’t want to leave them hanging so I set about using a 301 permanent redirect to solve this problem.
Fixing this is pretty straightforward, just a couple of lines of code. For me this the following placed near the top of index.php does the trick.
if ($_GET['wl_mode'] == 'rss') {
header("HTTP/1.1 301 Moved Permanently");
header("Location: http://" . $_SERVER['SERVER_NAME'] . "/blog/feed");
exit();
}
It looks for the get parameter wl_mode to be ‘rss’. If wl_mode is defined and equal to ‘rss’ it sets two headers in the response and then exits. The first tells the client to redirect and that the redirect is permanent. The second gives the location to redirect to, the server name of the request, from the variable so that it matches whatever hostname the request was made to and the path of WordPress’s RSS feed, ‘/feed’. The ‘/blog’ is where WordPress is installed on my site, if your root is WordPress you’d just have ‘/feed’.
What if your old url wasn’t wl_mode=rss. If it’s a different parameter or set of parameters you’d just swap them out. What if the old feed is not a parameter, but a URL/path? Something like the snippet below should be useful there.
if ($_SERVER['REQUEST_URI'] == '/blog/old/feed/path') {
header("HTTP/1.1 301 Moved Permanently");
header("Location: http://" . $_SERVER['SERVER_NAME'] . "/blog/feed");
exit();
}
Creating a custom wordpress theme is really easy especially if you’re starting with a template (a site design you want to use.) This is often the case when you’re trying to add a blog to an existing site or convert an existing website you’re happy with to use wordpress for blogging/content management. I won’t go in to details about how to install wordpress, there’s already a great guide for that. I’ll just outline the steps involved in creating a custom them to get wordpress to look & feel the way you want it to.
We’ll start out creating a directory to house our theme files (there’s only going to be 2 of them.) To do that we’ll log on to our server and execute the following:
$ cd /whereever/wordpress/is/installed/wp-content/themes $ mkdir custom
If you don’t have shell access to you server use whatever mechanism you’ve uploaded/edited the sites files with in the past.
There’s only two files required to create a template for wordpress, index.php and style.css. We’ll start with index.php. To create an initial version of this file we’ll pick up where we left off a minute ago and do the following. If you’re familiar with another editor, feel free to use it, choices include vi, emacs, … but pico is one of the simplest to use (ctrl-O to save, ctrl-X to exit, more commands are listed across the bottom.)
$ cd custom $ pico index.php
That will start up pico editing a file named index.php, the main template file for you new custom theme. We’ll start with a simple html page you can copy-n-paste in to this file.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" <?php language_attributes(); ?>>
<head>
<meta http-equiv="Content-Type" content="<?php bloginfo('html_type'); ?>;
charset=<?php bloginfo('charset'); ?>" />
<title>
<?php wp_title('«', true, 'right'); ?> <?php bloginfo('name'); ?>
</title>
<link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); ?>"
type="text/css" media="screen" />
<link rel="alternate" type="application/rss+xml"
title="<?php bloginfo('name'); ?> RSS Feed"
href="<?php bloginfo('rss2_url'); ?>" />
<link rel="alternate" type="application/atom+xml"
title="<?php bloginfo('name'); ?> Atom Feed"
href="<?php bloginfo('atom_url'); ?>" />
<link rel="pingback" href="<?php bloginfo('pingback_url'); ?>" />
</head>
<body>
<div id='header'>
Insert Your Header HTML here
</div>
<div id='content' class='span-16 prepend-1'>
<?php if (have_posts()) : ?>
<?php while (have_posts()) : the_post(); ?>
<div <?php post_class() ?> id="post-<?php the_ID(); ?>">
<h2><a href="<?php the_permalink() ?>" rel="bookmark"
title="Permanent Link to <?php the_title_attribute();
?>"><?php the_title(); ?></a></h2>
<small>
<?php the_time('F jS, Y') ?>
<!-- by <?php the_author() ?> -->
</small>
<div class="entry">
<?php the_content('Read the rest of this entry »'); ?>
</div>
<p class="postmetadata"><?php the_tags('Tags: ', ', ', '<br />');
?> Posted in <?php the_category(', ') ?> |
<?php edit_post_link('Edit', '', ' | '); ?>
<?php comments_popup_link('No Comments »',
'1 Comment »',
'% Comments »'); ?>
</p>
</div>
<?php endwhile; ?>
<div class="navigation">
<div class="alignleft"><?php
next_posts_link('« Older Entries') ?></div>
<div class="alignright"><?php
previous_posts_link('Newer Entries »') ?></div>
</div>
<?php else : ?>
<h2 class="center">Not Found</h2>
<p class="center">Sorry, but you are looking for something that isn't
here.</p>
<?php get_search_form(); ?>
<?php endif; ?>
</div>
<div id='sidebar' class='span-6 last'>
<?php get_sidebar(); ?>
</div>
<div id='footer'>
Insert Your Footer HTML here
</div>
</body>
</html>
Don’t worry if that looks like a mass of gibberish, there’s only a small portion of it that you’ll have to worry about, the two sections in red. In them you will place your header and footer HTML, whatever logos and/or text you’d like to see at the top of the page. If you’d like to have a navagation bar across the page you can create a second div following the header dive and put links to the various sections of you site there. The footer is a good place to put a copyright notice, links to email you or any other information you’d like to have appear at the bottom of all of your pages.
If you’re working with an existing template you want to insert wordpress into, you’ll take the section in blue and place it in the content section of your template. You may have to mess around with it a bit to get exactly what you’re looking for, but keep at it it shouldn’t take too long.
We’re half the way to a new custom WordPress theme. The next thing we’ll need to do is create style.css.
$ pico style.css
At this point if you want to save the file you can go to the admin section for you blog and click on the ‘Appearance’ link and you should see your new ‘custom’ theme. Clicking on it should pop up a preview of what your blog will look like using this theme. It probably won’t look like much yet, but it’s a nice clean workspace in which you’ll be able to mold things to your liking. If you don’t have visitors to your blog yet, or don’t mind them seeing the work in progress you may go head and apply your new theme. If you’re not ready for that you’ll need to continue to use the preview feature to view your work.
So one of the biggest problems with this theme is the sidebar is way down at the bottom below all of the content. We’ll need to add some css to address this issue, luckily there’s not much to it, at least to move the sidebar up. You’ll just need to add the following to style.css and refresh.
#header
{
}
#content
{
float: left;
width: 600px;
}
#sidebar
{
float: left;
width: 200px;
}
#footer
{
clear: both;
}
The css above makes both #content and #sidebar float left and then limits #content’s width to 600 pixels and the sidebar to 200. So the blog will be 800 pixles wide. The only other thing going on is that we’ve asked the footer to clear both, which essentially means that it should go below any floating divs before it. This is obviously pretty rudimentary and doesn’t do much for the ascetic appeal of our blog, but everything “works” from here it’s just fiddling with css (which is way beyond the scope of this post.) Take a look at the HTML generated by this theme using view source and you should be able to track down the id’s and class’s you need to address to shape things up. Web developer Tool-bar can be really helpful for this work, check it out.
So we’ve created a simple, although still ugly, wordpress theme from scratch. It uses lots of defaults that can be customized to your liking, but it’s a good start. If you have any questions feel free to hit me up at rwmcfa1 <at> neces.com. Don’t have the time and/or desire to mess with custom wordpress instalation/development get in touch.
Update: the scripts/process outlined here has been used as the foundation for zfs-periodic in the FreeBSD ports collection, you can check it out here.
ZFS on FreeBSD is powerful, especially when coupled with periodic taking hourly, daily, weekly, monthly, … snapshots. In the following post I’ll provide the scripts & config necessary to customize and walk you step-by-step through setting up zfs snapshots and scrubs with periodic on FreeBSD.
Periodic’s main advantage over the more traditional and obvious method of running a script from a cron job is integration with the notification emails and standard configuration mechanism. That may not sound like much, but that means you a year down the road (or someone else that comes to the system) only has to look in the obvious place to figure out what’s going on or make changes.
This is going to be a long post, but there’s a decent amount of code & config to walk through. The files being discussed have been tar’d up and the latest version of them can be downloaded from here.
We’ll start with the configuration (/etc/periodic.conf) as it’s the most relevant portion or at least the most likely to be edited. Out of the box FreeBSD supports daily, weekly, and monthly periodic tasks, we’re going to be adding an hourly so that we can do hourly snapshots. The first section of config sets up who output from the hourly script should go to, whether it should be sent if everything succeeded, if something failed, or if something is mis-configured. Hourly emails seem a bit much so we’ve disabled them when everything goes well. We do want messages about errors and I’ve just left badconfig to the same value as all of the other time-frames.
# Hourly options hourly_output="root" # user or /file hourly_show_success="NO" # scripts returning 0 hourly_show_info="YES" # scripts returning 1 hourly_show_badconfig="NO" # scripts returning 2
The next section configures hourly snapshots. In this case we’re enabling them for the pool tank and keeping the 6 most recent around. There are defaults, that we’ll see later, for both pools and keep so the only required value here is enable. To specify more than one pool add them space seperated to the config string, e.g. “tank boat plane”
# 000.zfs-snapshot hourly_zfs_snapshot_enable="YES" hourly_zfs_snapshot_pools="tank" hourly_zfs_snapshot_keep=6
The daily section is almost identical, but we instead keep the last 7 days. We’re also enabling a daily zfs status script that is in the default setup, but disabled.
# Daily options # 000.zfs-snapshot daily_zfs_snapshot_enable="YES" daily_zfs_snapshot_pools="tank" daily_zfs_snapshot_keep=7 # 404.status-zfs daily_status_zfs_enable="YES"
Weekly and Monthly have the same configuration options, we’re keeping the last 5 weeks, and last 2 months below.
# Weekly options # 000.zfs-snapshot weekly_zfs_snapshot_enable="YES" weekly_zfs_snapshot_pools="tank" weekly_zfs_snapshot_keep=5 # Monthly options # 000.zfs-snapshot monthly_zfs_snapshot_enable="YES" monthly_zfs_snapshot_pools="tank" monthly_zfs_snapshot_keep=2
A final section configures the monthly scrubbing. Similarlly to the snapshot config sections there’s an enable line and pools line. Here we’ve enabled the monthly scrub on the tank pool.
# 998.zfs-scrub monthly_zfs_scrub_enable="YES" monthly_zfs_scrub_pools="tank"
The next thing we need to do is add hourly support to periodic. While that might sound complicated it’s actually very straightforward. We start by creating a directory to house the hourly files.
# mkdir /etc/periodic/hourly
And then add the following line to /etc/crontab just before the line for ‘periodic hourly’
1 * * * * root periodic hourly
That’s it you now have a place to put scripts that will be run every hour on the :01.
Now we’ll get to the scripts that make all of this configuration do something. It’s unlikely that you’ll ever have to much with any of these, but in case your curious I’ll go ahead and walk though them. We’ll start with the hourly snapshot script (/etc/periodic/hourly/000.zfs-snapshot.)
1 #!/bin/sh 2 3 # If there is a global system configuration file, suck it in. 4 # 5 if [ -r /etc/defaults/periodic.conf ] 6 then 7 . /etc/defaults/periodic.conf 8 source_periodic_confs 9 fi 10 11 pools=$hourly_zfs_snapshot_pools 12 if [ -z "$pools" ]; then 13 pools='tank' 14 fi 15 16 keep=$hourly_zfs_snapshot_keep 17 if [ -z "$keep" ]; then 18 keep=6 19 fi 20 21 case "$hourly_zfs_snapshot_enable" in 22 [Yy][Ee][Ss]) 23 . /etc/periodic/zfs-snapshot 24 do_snapshots "$pools" $keep 'hourly' 25 ;; 26 *) 27 ;; 28 esac
Lines 3-9 is boilerplate periodic script stuff. 11-19 look for the values we configured earlier and use defaults if they’re not specified. 21, 22, 25, and 26 are case shell scripting case statement stuff that’s borrowed from one of the other periodic scripts, mainly just makes sure that hourly_zfs_snapshot_enable is set to YES, ignoring case. Line 23 pulls in (think #include) some common zfs snapshotting code that we’ll get to next and finally line 24 calls the snapshotting function for the configured pools, keep count, and the type of hourly. The daily, weekly, and monthly scripts are identical with hourly replaced with the appropriate value throughout.
There’s too much here to walk though in detail so I’ll let you read through the code. I’ve tried to do a decent job of in-line commenting. If you have questions or want clarification feel free to ask…
#!/bin/sh
# checks to see if there's a scrub in progress
scrub_in_progress()
{
pool=$1
if zpool status $pool | grep "scrub in progress" > /dev/null; then
return 0
else
return 1
fi
}
# take the appropriately named snapshot
create_snapshot()
{
pool=$1
case "$type" in
hourly)
now=`date +"$type-%Y-%m-%d-%H"`
;;
daily)
now=`date +"$type-%Y-%m-%d"`
;;
weekly)
now=`date +"$type-%Y-%U"`
;;
monthly)
now=`date +"$type-%Y-%m"`
;;
*)
echo "unknown snapshot type: $type"
exit 1
esac
# create the now snapshot
snapshot="$pool@$now"
# look for a snapshot with this name
if zfs list -H -o name | sort | grep "$snapshot$" > /dev/null; then
echo " snapshot, $snapshot, already exists"
else
echo " taking snapshot, $snapshot"
zfs snapshot -r $snapshot
fi
}
# delete the named snapshot
delete_snapshot()
{
snapshot=$1
echo " destroying old snapshot, $snapshot"
zfs destroy -r $snapshot
}
# take a type snapshot of pool, keeping keep old ones
do_pool()
{
pool=$1
keep=$2
type=$3
# create the regex matching the type of snapshots we're currently working
# on
case "$type" in
hourly)
# hourly-2009-01-01-00
regex="$pool@$type-[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]-[0-9][0-9]$"
;;
daily)
# daily-2009-01-01
regex="$pool@$type-[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]$"
;;
weekly)
# weekly-2009-01
regex="$pool@$type-[0-9][0-9][0-9][0-9]-[0-9][0-9]"
;;
monthly)
# monthly-2009-01
regex="$pool@$type-[0-9][0-9][0-9][0-9]-[0-9][0-9]"
;;
*)
echo "unknown snapshot type: $type"
exit 1
esac
create_snapshot $pool $type
# get a list of all of the snapshots of this type sorted alpha, which
# effectively is increasing date/time
# (using sort as zfs's sort seems to have bugs)
snapshots=`zfs list -H -o name | sort | grep $regex`
# count them
count=`echo $snapshots | wc -w`
if [ $count -ge 0 ]; then
# how many items should we delete
delete=`expr $count - $keep`
count=0
# walk through the snapshots, deleting them until we've trimmed deleted
for snapshot in $snapshots; do
if [ $count -ge $delete ]; then
break
fi
delete_snapshot $snapshot
count=`expr $count + 1`
done
fi
}
# take snapshots of type, for pools, keeping keep old ones,
do_snapshots()
{
pools=$1
keep=$2
type=$3
echo ""
echo "Doing zfs $type snapshots:"
for pool in $pools; do
if scrub_in_progress $pool; then
echo " skipping snapshot of $pool, scrub in progress"
else
do_pool $pool $keep $type
fi
done
}
I installed wordpress and imported all of my old blog posts (out of a simplistic php script blog I found 4 or 5 years ago, had to write a bit of code for that) a while back. At the time I had just redone the neces.com front page and I looked around a bit for a theme that would let me get a similar look & feel to that work. I didn’t find anything that started out close enough, but did manage to find a theme based on Blueprint Css. I had used Blueprint for the main site layout after using it with neumerous rails projects and generally liked working with it. However the wordpress theme based on it was a mess, and in general useless. I gave up and just left it alone…
Fast forward to last night and for some reason I decided I really did want my blog to look like my site. This time around I decided the best way to do that would be to create a theme from scratch. About 10 minutes later I had a copy of the latest wordpress up and running on my box at home and about 5 mintues after that I had something that was about 90% of the way to what you see now. It was redicously easy. I did a search or two on what’s involved in creating a theme, 2 mintues or so. Then I just took the template I created for neces, and stuck the wordpress content section in my neces content section, we’re at 3 mintues (elapsed) now. And finally created a second div for the sidebar (trivial with blueprint.) and stuck the wordpress sidebar code in it, ~5 minutes.
The rest of the work was CSS and took about 20 mintues to do this morning, fiddling around with various tweaks, between the shower and leaving for work. I’m pretty happy with the results. Now if my gallery, Gallery2.0, were only this easy to skin…
“Failure is always an option” – Adam – Mythbusters S07E01 – 09
I ran in to an interesting problem that took me a little bit of digging/thinking to figure out this morning. When you do a zpool scrub on FreeBSD and then do zfs snapshot the scrub restarts from the beginning, (at least as of this writing.) I couldn’t find any references to this and FreeBSD, but did find mentions of zfs scrub resetting with OSX. The same thread claimed the issue was addressed in OpenSolairs versions past that which had been ported/integrated in to OSX, probably the same for FreeBSD. I started a scrub last night before I went to bed and woke up this morning and it had less % done than it did the last time I looked, that’s not good. I checked in on it every few minutes for a while and noticed that it was completing pretty fast, but then kicked back up after a while. It didn’t immediately occur to me that it was at the top of the hour when my snapshot script had just run, but I got there a few minutes later.
At any rate, once I knew what was going on it made perfect sense and was pretty easily addressed. As part of addressing it I’ve generalized my snapshot setup and converted it to be run by periodic. A post with that is coming as soon as I live with it for a bit and make sure the kinks are worked out. It has actually turned out really cool, hourly, daily, weekly, monthly snapshots, monthly scrubs (during which snapshots are suspected and it’s all configurable…
A few months back I read a book titled A Short History of Nearly Everything. It really enjoyed the book. It was chocked full of interesting history, related people and developments, and factoids. One of the simplest and best was that the human body has about 10x the bacterial cells as human. That’s staggering enough, 1 trillion human cells, 10 trillion bacterial, but a great presentation I just watched on the communication mechanisms of bacterial cells added that there’s about 100 x more genetic code in those bacteria.
The presentation is about the ways in which bacteria communicate. Apparently there is both an intra and inter-species mechanisms and scientists has successfully mimicked the molecules (hormones) involved. The hope is the work will lead to the next generation of antibiotics (a development that is seriously needed.) Check out the talk, one of many great TED talks.