# !/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 > /tmp/postit
for category in $categories
do
    echo category/$category/index.html >> /tmp/postit
    echo category/$category/1/index.html >> /tmp/postit
    echo category/$category/feed/index.xml >> /tmp/postit
    echo category/$category/feed/atom/index.xml >> /tmp/postit
done
echo archive/$archive/1/index.html>> /tmp/postit
echo feed/index.xml >> /tmp/postit
echo feed/atom/index.xml >> /tmp/postit
echo page/1/index.html>> /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 

• flat files are almost impossible to hack
• Amazon's S3 (Simple Storage System) can scale incredibly high

• blogofile build seems to copy or regenerate every single file
• it's not totally happy being on S3 - it doesn't make index.html files for the archive and category directories.
• there's no easy way to post-via-email or send a link to start a post

What was really appalling to me was getting burned by this screen:

Twitter, like Facebook, lets you use other sites by handling authorization. I’d been having serious problems with Twitter not accepting my password (as were thousands of others, apparently) and it just got fixed last week. So even though I was logged in and active on twitter.com, I wasn’t surprised to be prompted to login. And I didn’t look closely enough at the URL.

Of course I wasn’t surprised to see this:

Takeaways? Twitter has becoming more and more reliable. They are fixing bugs. And we all need to watch where we’re going - sometimes we think we’re someplace we’re not.

images courtesy of Sophos I copied them so they won’t take their bandwidth or disappear if they change their links.

My only objection is that it’s not posted to UserScripts, a central repository for Greasemonkey scripts.

Smart Google Reader Subscribe Button is highly recommended.

It’d be nice to look into later.