<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:wfw="http://wellformedweb.org/CommentAPI/"
     >
  <channel>
    <title>Sirius Stuff</title>
    <link>http://www.siriusventures.com/</link>
    <description>A static blog engine/compiler</description>
    <pubDate>Fri, 29 Apr 2011 19:21:34 GMT</pubDate>
    <generator>Blogofile</generator>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Script to update Blogofile blog on Amazon S3</title>
      <link>http://www.siriusventures.com/script-to-update-blogofile-blog-on-amazon-s3</link>
      <pubDate>Fri, 29 Apr 2011 15:00:10 PDT</pubDate>
      <category><![CDATA[Blogging]]></category>
      <guid>http://www.siriusventures.com/script-to-update-blogofile-blog-on-amazon-s3</guid>
      <description>Script to update Blogofile blog on Amazon S3</description>
      <content:encoded><![CDATA[<br/>Because <a title="blogofile" href="http://www.blogofile.com">Blogofile</a>Blogofile (at least the 0.7.1 version I'm using) regenerates every file and directory every time it makes it hard to update just the changed files on &gt;<a title="amazon" href="http://www.amazon.com/">Amazon</a>'s <a title="s3" href="http://aws.amazon.com/s3/">S3</a> (Simple Storage System).
<br/>
So I wrote a shell script that updates only the changed files and also pings <a href="http://www.googleping.com/" title="GooglePing">GooglePing</a> so that Google and other services come along and read your update.
<br/>
Over time, the difference between what the old page 2 on S3 has and what it should be will build.  There's a simple answer, which is to just upload all of the page files.  
<br/>
Every 10 blog posts or so, you could just update all the category and archive files as well.   Maybe that's somthing to automate as well
<br/><pre>

# !/bin/bash
# jdeibele [ at ] gmail . com
# What this does:
#   builds your blog with blogofile, then builds a list of key 
#   files that have changed.  Blogofile is a python program
#   that uses Mako to generate static pages.
#
# Blogofile: http://www.blogofile.com
#
# For me, these files are:
#   the post itself
#   the first page of the categories it appears in 
#   feeds for the categories (RSS and atom)
#   the archive page (year/month) 
#   the first page of /page/
#   feed for the blog (RSS and atom)
#   the main page (index.html) for the blog
#
#
BLOGURL="www.siriusventures.com"
BLOGNAME="Sirius Stuff"
BLOGHOME=$HOMEDIR/siriusventures
#
#
cd $BLOGHOME 
blogofile build
rmdir *
# blogofile builds extra directories for these but they're empty
cd $BLOGHOME/_posts
file=`ls -t * | head -1`
permalink=`grep "^permalink:" $file | cut -f3 -d: | cut -f4 -d"/"`
archive=`grep "^date:" $file | cut -f2 -d: | cut -f1,2 -d/ | sed 's/ //g'`
#
# "slugify" the category names 
#
categories=`grep "^categories:" $file | tr [:upper:] [:lower:]  | cut -f2 -d: | sed s'/^ //' | sed s'/ /-/'`
echo $categories
cd $BLOGHOME/_site
IFS=','
echo index.html &gt; /tmp/postit
for category in $categories
do
    echo category/$category/index.html &gt;&gt; /tmp/postit
    echo category/$category/1/index.html &gt;&gt; /tmp/postit
    echo category/$category/feed/index.xml &gt;&gt; /tmp/postit
    echo category/$category/feed/atom/index.xml &gt;&gt; /tmp/postit
done
echo archive/$archive/1/index.html&gt;&gt; /tmp/postit
echo feed/index.xml &gt;&gt; /tmp/postit
echo feed/atom/index.xml &gt;&gt; /tmp/postit
echo page/1/index.html&gt;&gt; /tmp/postit
# 
# s3cmd can be installed with homebrew - brew install s3cmd
#
#
# s3cmd needs -recursive to upload a new directory
#
s3cmd put --recursive $BLOGHOME/_site/$permalink s3://$BLOGURL
#
while read file
do
    s3cmd put $BLOGHOME/_site/$file s3://$BLOGURL/$file
    echo $BLOGHOME/_site/$file
done 
<br/></pre>]]></content:encoded>
    </item>
    <item>
      <title>What's not perfect with Blogofile</title>
      <link>http://www.siriusventures.com/whats-not-perfect-with-blogofile</link>
      <pubDate>Thu, 28 Apr 2011 15:00:10 PDT</pubDate>
      <category><![CDATA[Web]]></category>
      <category><![CDATA[User Interface]]></category>
      <category><![CDATA[Blogging]]></category>
      <guid>http://www.siriusventures.com/whats-not-perfect-with-blogofile</guid>
      <description>What's not perfect with Blogofile</description>
      <content:encoded><![CDATA[<br/>In <i><a href="http://www.siriusventures.com/switched-from-wordpress-to-blogofile" title="Switched from WordPress to Blogofile">Switched from WordPress to Blogofile</a></i> there are two good things about using <a title="blogofile" href="http://www.blogofile.com">Blogofile</a>:
<ul><li>flat files are almost impossible to hack</li>
<li><a title="amazon" href="http://www.amazon.com/">Amazon</a>'s <a title="s3" href="http://aws.amazon.com/s3/">S3</a> (Simple Storage System) can scale incredibly high</li>
</ul><br/><br/>
There's some downsides:
<ul><li><i>blogofile build</i> seems to copy or regenerate every single file</li>
<li>it's not totally happy being on S3 - it doesn't make index.html files for the archive and category directories.  
</li><li>there's no easy way to post-via-email or send a link to start a post</li>
</ul><br/><br/>
Right now I'm writing this with vi and that's far less comfortable than WordPress's editor which I really liked.   But I'm sure I'll find TextWrangler or something as suitable for writing blog posts.
<br/>]]></content:encoded>
    </item>
    <item>
      <title>Celebrity Worship and the American Dream · Violent Acres</title>
      <link>http://www.siriusventures.com/celebrity-worship-and-the-american-dream-%c2%b7-violent-acres/</link>
      <pubDate>Fri, 15 Jun 2007 06:06:06 PDT</pubDate>
      <category><![CDATA[Blogging]]></category>
      <guid>http://www.siriusventures.com/celebrity-worship-and-the-american-dream-%c2%b7-violent-acres/</guid>
      <description>Celebrity Worship and the American Dream · Violent Acres</description>
      <content:encoded><![CDATA[
				<p id="p1">Love this quote from <a href="http://www.violentacres.com/">Violent Acres</a> about <a href="http://www.violentacres.com/archives/204/celebrity-worship-and-the-american-dream">Celebrity Worship and the American Dream</a></p>
<blockquote><p id="p2">Speaking of the American dream, has anyone noticed how much it’s changed? The American dream used to be about owning a modest home, having a happy family, and supporting yourself with honest, hard work. No one vies for things like that anymore.</p></blockquote>
<p id="p3">She certainly expresses herself in ways that I wouldn’t.  But like the way so many of her posts cut to the heart of things.  Recommended reading.
</p>
]]></content:encoded>
    </item>
    <item>
      <title>Google Reader Optimized</title>
      <link>http://www.siriusventures.com/google-reader-optimized/</link>
      <pubDate>Wed, 13 Jun 2007 06:06:06 PDT</pubDate>
      <category><![CDATA[Blogging]]></category>
      <guid>http://www.siriusventures.com/google-reader-optimized/</guid>
      <description>Google Reader Optimized</description>
      <content:encoded><![CDATA[
				<p id="p1">I’ve been using Google Reader more and more.  I’m not thrilled with the layout, so I was really pleased to see that I could modify it either using the <a href="https://addons.mozilla.org/firefox/2108/">Stylish FireFox Extension</a> or via <a href="https://addons.mozilla.org/en-US/firefox/addon/748">Greasemonkey</a> <a href="http://userstyles.org/styles/1236">Google Reader Optimized</a></p>
<p id="p2">I started out with Stylish but am trying to cut down on the number of extensions I have.  Of course, whether it’s better to have it as a Greasemonkey script seems more open to problems than an extension.   You’re one level away from the scripts and they don’t go through the official Mozilla check-in process. </p>
]]></content:encoded>
    </item>
    <item>
      <title>I'm Sorry You Feel That Way</title>
      <link>http://www.siriusventures.com/im-sorry-you-feel-that-way/</link>
      <pubDate>Tue, 29 May 2007 05:05:05 PDT</pubDate>
      <category><![CDATA[Blogging]]></category>
      <category><![CDATA[General]]></category>
      <guid>http://www.siriusventures.com/im-sorry-you-feel-that-way/</guid>
      <description>I'm Sorry You Feel That Way</description>
      <content:encoded><![CDATA[
				<p id="p1">Wow, this is a great post.  <a href="http://www.violentacres.com/archives/187/pet-peeve-7-im-sorry-you-feel-that-way">Pet Peeve #7: I’m Sorry You Feel That Way · Violent Acres</a> totally sums up how snotty some people are when saying “I’m sorry you feel that way”.  Wow.</p>
]]></content:encoded>
    </item>
    <item>
      <title>This is the way I&#8217;m feeling about technology, too</title>
      <link>http://www.siriusventures.com/this-is-the-way-im-feeling-about-technology-too/</link>
      <pubDate>Tue, 27 Mar 2007 03:03:03 PDT</pubDate>
      <category><![CDATA[User Interface]]></category>
      <category><![CDATA[Blogging]]></category>
      <category><![CDATA[General]]></category>
      <guid>http://www.siriusventures.com/this-is-the-way-im-feeling-about-technology-too/</guid>
      <description>This is the way I&#8217;m feeling about technology, too</description>
      <content:encoded><![CDATA[<p id="p1">I found Eric Sink’s blog via some references from <a href="http://www.joelonsoftware.com/">Joel Spolsky</a>’s blog.  This is a <a href="http://software.ericsink.com/entries/Technology_Dependence.html">nice post</a> about the problems with whiz-bang technology.  
</p>
]]></content:encoded>
    </item>
    <item>
      <title>What I now know about Wordpress 2.1</title>
      <link>http://www.siriusventures.com/what-i-now-know-about-wordpress-21/</link>
      <pubDate>Sun, 28 Jan 2007 01:01:01 PST</pubDate>
      <category><![CDATA[Open Source]]></category>
      <category><![CDATA[Blogging]]></category>
      <guid>http://www.siriusventures.com/what-i-now-know-about-wordpress-21/</guid>
      <description>What I now know about Wordpress 2.1</description>
      <content:encoded><![CDATA[<p id="p1">is that I can’t run it because my host is running MySQL prior to 4.0.   Tried doing the upgrade and it sort of worked … but not really.  So I reverted back to 2.0.6 and found 2.0.7 which is what we’re running now.  Really have to get credit to the folks at <a href="http://wordpress.org">WordPress</a> - they have made a solid piece of software that’s easy enough to work with that many people have made plug-ins … but it handles stuff like 2.0.6-&gt;2.1-&gt;2.0.7 without messing up.  Very comfortable feeling, relying on it.</p>
<p id="p2"><a href="http://www.technosailor.com/10-things-you-should-know-about-wordpress-21/">10 Things You should Know About WordPress 2.1 » Technology, Blogging and New Media</a> is a good summary of key changes.</p>
<blockquote><p id="p3"><strong>Merging of Links and Categories</strong> […] While those philosophies can be discussed in other posts, the important<br/>
thing to recognize is that the Categories table is now prepopulated<br/>
with a Blogroll category and all links are assigned, by default, to the<br/>
blogroll category. </p></blockquote>
<p id="p4">That’s actually something I’d like to have.  Trying to make two sets of categories is a pain.  Much nicer to link to Wordpress.org in the blogging category, etc.</p>
<p id="p5">So I just need to figure out how to back up my blog, then make WordPress work on a different port.  Yeah, easy-peasy.  But I will get to it so I can see what the other features are like.
</p>
]]></content:encoded>
    </item>
    <item>
      <title>Seattleite patronizing Portland again</title>
      <link>http://www.siriusventures.com/seattleite-patronizing-portland-again/</link>
      <pubDate>Sun, 28 Jan 2007 01:01:01 PST</pubDate>
      <category><![CDATA[Portland]]></category>
      <category><![CDATA[Blogging]]></category>
      <category><![CDATA[General]]></category>
      <guid>http://www.siriusventures.com/seattleite-patronizing-portland-again/</guid>
      <description>Seattleite patronizing Portland again</description>
      <content:encoded><![CDATA[
				<p id="p1">I enjoy reading <a href="http://360digest.com/">360digest</a> when I get a chance.  Not only is my brother-in-law Dave a newly-minted real estate agent but the house next door was up for sale for a while recently.  Real estate is one of those things that we all have to deal with, because we all need a place to live.</p>
<p id="p2">Anyway, I was amused to read that on the blog this quote:</p>
<p id="p3"><em>In Portland, Ore., $300,000 means a clean and simple floating home on the Pacific ocean</em></p>
<p id="p4">Ummm, it would not be a clean and simple home.  Because the Pacific Ocean is 90 miles away from Portland, which is on the Columbia and Willamette <strong>rivers</strong>.  </p>
<p id="p5">100 years ago, Portland was a more significant city than Seattle because of those rivers.  It was simply easier to float things up and down the rivers than to try to move them across land.  With trucks and interstates and container ships, that’s changed significantly.  Now it’s important to have deep water and make it easy for big ships to navigate into docks as quickly as possible.   So new Portland is “little sister” to Seattle.  Which never lets us forget it.  <img src="http://www.siriusventures.com/wp-includes/images/smilies/icon_smile.gif" alt=":-)" class="wp-smiley"/>
</p>
]]></content:encoded>
    </item>
    <item>
      <title>pingback versus trackback explained</title>
      <link>http://www.siriusventures.com/pingback-versus-trackback-explained/</link>
      <pubDate>Thu, 30 Mar 2006 03:03:03 PST</pubDate>
      <category><![CDATA[Blogging]]></category>
      <guid>http://www.siriusventures.com/pingback-versus-trackback-explained/</guid>
      <description>pingback versus trackback explained</description>
      <content:encoded><![CDATA[<p id="p1">I’ve never really understood the differences between “pingback” and “trackback”.  Google likes to display older articles, which has interesting effects  The first thing that I found that tried to explain the differences was published more than 3 years ago and has way more detail than I want.  But this <a href="http://ln.hixie.ch/?start=1033171507&amp;count=1">whitepaper</a> led me to more resources on pingback and trackback.</p>
<p id="p2">If I can summarize:</p>
<p id="p3">Pingback
</p><ul><li>Just ping a blog (or whatever) with your own blogging software</li>
<li>No detail about what you said about them</li>
<li>Receiver doesn’t link back to you</li>
</ul><p id="p4">Trackback
</p><ul><li>Details about what was said</li>
<li>Receiver can link back if they want.  </li>
</ul><p id="p5">SixApart has a <a href="http://www.sixapart.com/pronet/docs/trackback_spec">trackback technical doc</a> that explains more.
</p>
]]></content:encoded>
    </item>
  </channel>
</rss>

