Fetching contributors…
Cannot retrieve contributors at this time
198 lines (134 sloc) 4.98 KB
This is Lame Blog.
A small script that I wrote to maintain my blog on the web. I
did not use another blog system, because I had different
requirements than other people have.
I wanted:
* To support off-line editing. Since for long periods
of time I might not have an internet connection.
* To be able to edit my blog entries with my choice
editor, not using some integrated tool.
* To keep my old .txt file format for my entries.
* To do some minimal processing on the input.
To configure LameBlog, you must create a file config.xml, which
looks like this:
<?xml version="1.0"?>
Author="Miguel de Icaza ("
Copyright="Miguel de Icaza"
Description="Miguel de Icaza's web log"
Title="Miguel de Icaza"
ThumbnailCommand="shell-command-for-thumbnail source={0} thumbnail={1}"
The various parameters should be self explanatory.
It looks for blog entries in:
Ie, for example:
For files with the HTML ending, it assumes that the title for
the blog entry will be the first line (which should be tagged
with <h1>title</h1>). This means:
<h1>This is my Title</h1>
For text files, the first line should be formatted like this:
@This is my Title
To add multiple entries per day, append a -N to the entry:
For historic reasons, it generates an all.html (compatibility
with old permalinks) and also now it generates per-day
permalink entries in the archive/ directory.
To run, you must type:
To upload, edit the settings on the Makefile, and type:
make push
The result is then pushed to a server with rsync.
The AnalyticsStub is the file provided to you by google as the
stub that you must insert.
Lame Blog also now supports Markdown-formatted files as blog
entries. They take the .md extension, and are regular Markdown
format. You can use the h1 Markdown tag (#) to denote the title
on the first line as well, because Markdown files are first
processed by MarkdownSharp into HTML, and then loaded as .html
files would be. MarkdownSharp is courtesy of Stack Overflow,
and can be found at
* Commands
The following commands can be used in your individual blog entries:
#include file
Will include the contents of "file" into the blog entry
#pic filename,caption
Will generate the code to center the image stored in
filename with the given caption.
This emits an HTML anchor to "pic.php" providing filename and
caption as GET parameters.
#comment, #comments
Will enable the entry to have comments. To activate
comments, you need to get a comment hosting provider,
and then paste the stub into the file `comments', or
the file referenced in the config.xml CommentsStub
#thumbnail filename caption
A static alternative to #pic. This looks for `filename'
underneath ImageDirectory, copies `filename' into the archive
directory, creates a thumbnail for `filename' by invoking
ThumbnailCommand, and generates HTML that is an <a><img/></a> to
the thumbnail which targets the full-size image.
Caption is used as the alt and title text of the <img/>.
A possible ThumbnailCommand value is:
convert -size 400x300 {0} -resize 400x300 +profile '&quot;*&quot;' {1}
which generates a 400x300 pixel thumbnail of the input file.
* Templates
The main blog template is the file "template", this contains
the general layout of the file and will do substitutious on a
number of fields:
Main template: "template" file
The title of the blog, this becomes the
Substituted with the contents specified in the
config file for "Analytics"
Replaced with the string in ManagingEditor
from the config file
Lists the articles that you want to link,
these are not the blog entries, but thinks
that you want on your sidebar.
The blog entries rendered.
Per entry template: "entry" file.
Anchor used to target an entry.
Produces HTML to move to the previous/main/next blog
Miguel de Icaza (