<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Most of this stuff about blogging/publishing tools has been debated
before on the list, but my $0.02 again:<br>
<br>
On 6/9/11 11:52 AM, The Doctor wrote:<br>
<br>
<span style="white-space: pre;">> It can use flat files on the
back end, and yes, it generates pages <br>
> dynamically using PHP.</span><br>
<br>
IMHO, requiring PHP on a plug computer and using it to serve pages
up to live web traffic is a non-starter. These things will likely be
on residential cable or DSL networks, or even on intermittent dialup
or mesh networking.<br>
<br>
<span style="white-space: pre;">>> Ikiwiki uses common VCS
(e.g. git or Subversion) as backend,<br>
>> compiles when editing, and serves static html files.<br>
> <br>
> How processor intensive would updating an Ikiwiki instance
be?<br>
</span><br>
Not very, especially when you consider that the processor usage only
happens at authoring time and not with every web request. Also, the
static files produced by ikiwiki can be pushed up to an intermediate
server like Amazon S3 or NearlyFreeSpeech to further deflect traffic
from a freedombox.<br>
<br>
My take on web publishing tools for a freedombox is that they should
give the owner control over authoring and publishing, but offer the
option to defer distribution to other intermediaries. You *can*
still host on your own box, but there's an escape hatch. That way, a
freedombox owner doesn't need to keep a web host healthy and
running.<br>
<br>
And, tools that produce static files (like Ikiwiki) help enable
that.<br>
<br>
--<br>
<a class="moz-txt-link-abbreviated" href="mailto:l.m.orchard@pobox.com">l.m.orchard@pobox.com</a><br>
<a class="moz-txt-link-freetext" href="http://decafbad.com">http://decafbad.com</a><br>
{web,mad,computer} scientist<br>
<br>
</body>
</html>