Go to file
Joey Hess bb44bac175 look up avatar at comment post time
There is a tension between looking up the avatar at post time
and build time. I have not yet decided which is better.

Lookup at build time has the benefit that if a user changes their
email address, or sets up their own federated libravatar
server, on rebuild their new avatar will show up.

It also allows getting a https version of the avatar easily if
the site was using http but was changed to use https.

And it can look up avatars for posts that have already been made.
Which is a nice thing, especially as we roll this out, eh?

But it has a drawback, that it depends on the sessiondb contents
for emails and so rebuilding a site w/o that will lose info.

And, it means dns lookups every time a comment is rendered. A page
with a lot of comments on it would render them all whenever another is
posted or the page is changed, and that could significantly slow things
down. (This could be amelorated by caching the lookups.)

Since I'm undecided, I have moved it into a function that could be called
either way. Currently looking up only at post time.
2011-03-30 11:24:01 -04:00
Bundle update for libravatar support 2011-03-30 10:55:36 -04:00
IkiWiki look up avatar at comment post time 2011-03-30 11:24:01 -04:00
cpan
debian update for libravatar support 2011-03-30 10:55:36 -04:00
doc Merge remote-tracking branch 'remotes/fmarier/libravatar-in-comments' 2011-03-30 10:44:38 -04:00
plugins
po releasing version 3.20110328 2011-03-28 12:30:57 -04:00
t get rid of diag explain again 2011-03-04 11:23:10 -04:00
templates comments: add avatar picture of comment author 2011-03-30 20:59:17 +13:00
themes tweak 2010-12-11 14:50:53 -04:00
underlays openid: Syntax tweak to the javascript code to make it work with MSIE 7 (and MSIE 8 in compat mode). Thanks to Iain McLaren for reporting the bug and providing access to debug it. 2010-08-17 16:05:17 -04:00
.gitattributes auto changelog merging 2010-06-25 13:43:02 -04:00
.gitignore extend the 'tag' test to cover auto-creation of tag pages 2010-12-25 22:54:54 +00:00
.perlcriticrc
CHANGELOG
IkiWiki.pm Yaml formatted setup files are now produced by default 2011-03-24 21:30:18 -04:00
Makefile.PL remove reundant chengelog version parse 2011-03-19 14:03:50 -04:00
NEWS
README parameterize FIND and SED 2010-09-27 16:10:13 -04:00
auto-blog.setup auto-blog.setup: Don't enable opendiscussion by default; require users be logged in to post comments. 2010-10-17 17:26:35 -04:00
auto.setup
docwiki.setup disable openid when building doc dir 2010-05-15 23:24:57 -04:00
gitremotes gitremotes: don't fetch the new remote until we've turned off tags 2010-05-09 16:44:47 +01:00
ikiwiki-calendar.in rcs_commit and rcs_commit_staged api changes 2010-06-23 19:04:36 -04:00
ikiwiki-makerepo
ikiwiki-mass-rebuild
ikiwiki-transition.in
ikiwiki-update-wikilist
ikiwiki-w3m.cgi
ikiwiki.in Remove PATH overriding code in ikiwiki script that was present to make perl taint checking happy, but taint checking is disabled. 2010-09-07 13:47:50 -04:00
ikiwiki.spec releasing version 3.20110328 2011-03-28 12:30:57 -04:00
mdwn2man sync mdwn2man changes from git-annex 2010-12-10 17:36:39 -04:00
pm_filter
wikilist

README

Use ./Makefile.PL to generate a Makefile, "make" will build the
documentation wiki and a man page, and "make install" will install ikiwiki.

All other documentation is in the ikiwiki documentation wiki, which is also
available online at <http://ikiwiki.info/>


A few special variables you can set while using the Makefile.PL:

  PROFILE=1 turns on profiling for the build of the doc wiki.
  (Uses Devel::NYTProf)

  NOTAINT=0 turns on the taint flag in the ikiwiki program. (Not recommended
  unless your perl is less buggy than mine -- see
  http://bugs.debian.org/411786)

  MAKE, FIND, and SED can be used to specify where you have the GNU
  versions of those tools installed, if the normal make, find, and sed
  are not GNU.

  There are also other variables supported by MakeMaker, including PREFIX,
  INSTALL_BASE, and DESTDIR. See ExtUtils::MakeMaker(3).

  In particular, INSTALL_BASE is very useful if you want to install ikiwiki
  to some other location, as it configures it to see the perl libraries
  there. See `doc/tips/nearlyfreespeech.mdwn` for an example of using this to
  install ikiwiki and its dependencies in a home directory.