 | |||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||
|
FAQ |
|||||||||||||||||||||||||||||||||||||||||||||||||
|
Folks: Bradley James Ladybug C.F. Rhodes, Phd. Two Blowhards. | |||||||||||||||||||||||||||||||||||||||||||||||||
Freaks:
| |||||||||||||||||||||||||||||||||||||||||||||||||
| Froth: | |||||||||||||||||||||||||||||||||||||||||||||||||
| Foam: | |||||||||||||||||||||||||||||||||||||||||||||||||
Sat, 27 Sep 2003
Bloxsom and console-based diary combined.
Here's how you do it. After downloading Bloxsom from Bloxsom.com, I edited the following lines so that it would make sense for the Athena environment. First I wrote a wrapper script that adds in the password option. On Athena, there is no non-command line context for invoking bloxsom, so that option should be unnecessary. More on the wrapper later.
In the script itself, some lines need to be modified:
# Where are this blog's entries kept?
$datadir = "$ENV{HOME}/www/bloxsom";
# What's my preferred base URL for this blog (leave blank for automatic)?
$url = "http://www.mit.edu/~$ENV{USER}";
[...]
# Where are my plugins kept?
# Users for the moment will have to mkdir this dir and
# put symlinks to plugins they want, which will
# point to plugins in /mit/outland/share/bloxom/plugins
$plugin_dir = "$ENV{HOME}/www/bloxsom/plugins";
[..]
# Where should my modules keep their state information?
$plugin_state_dir = "$plugin_dir/state";
This setup allows me to install the saner bloxsom
plugins in one place in AFS and then let users add symlinks
(or their own plugins in ~/www/bloxsom/plugins.
Then comes the
wrapper script. Without options it just
runs bloxsom so as to generate the HTML. With a
"-p foo" option, it sees if the outland folder has a plugin
named foo and puts a symbolic link to it if there is.
Next comes combining this tool with the console based diary. I already mentioned that in a previous entry. It involves taking the diary script, adding a $SUFFIX variable all over the place, changing all the ls command lines to use it properly, and assigning the variable the value ".txt." Presto, a non-HTTP web diary.
And here is a second test of the combination. Does it work if I feed it after midnight? Apparently not. For reasons I am not grokking, it insists on touching the last entry prior to the current one. Very odd, that. I think it's the task-list promotion part of the script that does that. I'll need to disable it. And it's time to for a little Google fudging, as requested by Dan Gillmor.
posted at: 20:45 | path: | permanent link to this entry
Trying too damn hard sometimes....
This is a test for combining Bloxsom with the
console-based-diary to make the most minimally
written Web diary available for people serving
static pages on machines where they have shell accounts.
The way to do it is to download the CBD from the link above,
diff it against
my modifications
and then set up a diaryrc file in their .diary that will direct
the CBD to put its entries in the Bloxsom directory and
give them the suffix ".txt",
like so.
Presto. Type "diary" to write the day's entry,
and "bloxsom" to process it with your Bloxsom templates
and what-have-you.
posted at: 00:28 | path: | permanent link to this entry
