This is where announcements of new releases, features, and other news are posted. IkiWikiUsers are recommended to subscribe to this page's RSS feed.
ikiwiki 2.53.2 released with these changes
- Fix bad patch backport that broke generation of rss/atom feeds. Closes: #498224
Quick poll: Do you feel that ikiwiki is fast enough on this server, or should I move it to my much beefier auxiliary server?
[[!poll open=no 40 "It's fast enough" 6 "It's too slow!" 4 "No opinion"]]
If you have specifics on performance issues, you might mention them on the discussion page.
The current server is a single processor 2.8 ghz Sepron machine shared among 4 other xen instances, and often heavily loaded by extraneous stuff like spamassassin and compiles. The auxiliary server is a dual processor, dual core 2 ghz Opteron shared with other xen instances (exact number not available from provider), but with little other load.
News for ikiwiki 2.60:
Admin preferences are moving from the web interface to the setup file.
There are three new options in the setup file: locked_pages
, banned_users
,
and allowed_attachments
. The admin prefs page can still be used, but
that's deprecated, and the prefs will be hidden if a value is not already
set. If a value is set in the web interface, you're encouraged to move that
setting to your setup file now, since version 3.0 will remove the deprecated
admin prefs web interface.
Also, the layout of the setup file has changed in a significant way in this
release. Old setup files will continue to work, but new features, like the
new websetup interface, require a new format setup file. You can convert
old setup files into the new format by running
ikiwiki-transition setupformat ikiwiki.setup
ikiwiki 2.60 released with these changes
- [ Joey Hess ]
- Starting with this version, "ikiwiki -setup /etc/ikiwiki/auto.setup" can be used create a new wiki in seconds.
- websetup: New plugin providing a setup form on the web.
- ikiwiki --dumpsetup can generate a nice setup file snapshotting ikiwiki's current configuration.
- The way wrappers are defined in the setup file has changed. Old setup files will continue to work, for now.
- ikiwiki-transition setupformat can be used to convert a setup file to the new format.
- Version control backends promoted to first-class plugins.
- ikiwiki-update-wikilist: Add -r switch to remove. Default behavior is now always to add.
- Start moving admin preferences from the web interface to the setup file.
- Add getsetup hook, all plugins should use it to record information about themselves and any fields they add to %config
- Large amounts of internal config data reorg.
- ikiwiki-makerepo: Bail if both srcdir and repository are not specified. Closes: #493628
- Clarify some wording in the setup documentation that could maybe lead users to putting paths with "~/" in the setup file, which doesn't work. Closes: #493835
- autoindex: Ignore internal pages, and take underlay directories into account. Also, avoid making index pages for directories that contain no files.
- external: Fix support for hooks called in an array context.
- Options set in the setup file are now immediatly loaded by ikiwiki -setup. This allows later switches to override them. Previously, setup file options overrode most command line options.
- Added a small icon to the search input box.
- [ Josh Triplett ]
- Add Suggests on texlive and texlive-science for the teximg plugin
- [ Joey Hess ]
- inline: Ignore parent dirs when sorting pages by title.
- rename: Support changing page extensions. (willu)
- Danish update. Closes: #494632
ikiwiki 2.56 released with these changes
- autoindex: New plugin that generates missing index pages. (Sponsored by The TOVA Company.)
- Escape HTML is rss and atom feeds instead of respectively using CDATA and treating it as XHTML. This avoids problems with escaping the end of the CDATA when the htmlscrubber is not used, and it avoids problems with atom XHTML using named entity references that are not in the atom DTD. (Simon McVittie)
- Add test for old versions of git that don't support --cleanup=verbatim, and munge empty commit messages.
ikiwiki 2.61 released with these changes
- poll: Fix typo that broke plugin.
- graphviz: Fix breakage of the name of the preprocessor directive.
Ikiwiki has reached version 2.0 and entered a new phase in its development cycle.
With the 2.0 release of ikiwiki, some major changes have been made to the default configuration:
- The
usedirs
setting is enabled by default. This will break all URLs to wikis that did not haveusedirs
turned on before, unless you follow the procedure described at switching to usedirs or edit your setup file to turnusedirs
off:usedirs => 0,
- OpenID logins are now enabled by default, if the
Net::OpenID::Consumer perl module is available. Password logins
are also still enabled by default. If you like, you can turn either OpenID
or password logins off via the
disable_plugins
setting.
An overview of changes in the year since the 1.0 release:
- New improved URLs to pages via
usedirs
. - OpenID support, enabled by default.
- Plugin interface added, with some 60 plugins available, greatly expanding the capabilities of ikiwiki.
- Tags, atom feeds, and generally full-fledged blogging support.
- Fully working utf8.
- Optimisations, approximately 3.5 times as fast as version 1.0.
- Improved scalability to large numbers of pages.
- Improved scalable logo.
- Support for additional revision control systems besides svn: git, tla, mercurial.
- Some support for other markup languages than markdown: rst, textile.
- Unit test suite, with more than 300 tests.
ikiwiki 2.62.1 released with these changes
- filecheck: Fixed two bits broken in move from attachment.
News for ikiwiki 2.62:
The teximg plugin now has a configurable LaTeX preamble.
As part of this change the mchem
LaTeX package has been removed from
the default LaTeX preamble as it wasn't included in many TeX installations.
The previous behaviour can be restored by adding the following to your
ikiwiki setup:
teximg_prefix => '\documentclass{scrartcl}
\usepackage[version=3]{mhchem}
\usepackage{amsmath}
\usepackage{amsfonts}
\usepackage{amssymb}
\pagestyle{empty}
\begin{document}',
In addition, the rendering mechanism has been changed to use dvipng
by
default, if available.
ikiwiki 2.62 released with these changes
- Avoid using cp -a (again). (HenrikBrixAndersen)
- Avoid using hostname -f for portability to eg, OS X, use Net::Domain instead, and prompt if it fails.
- Fix bug in wikiname sanitisation in the setup automator.
- ikiwiki-makerepo: Added support for monotone. (Thomas Keller)
- map: The fix for #449285 was buggy and broke display of parents in certian circumstances.
- teximg: The prefix is configurable, and has changed to not include the nonstandard mhchem by default. (willu)
- teximg: dvipng is used if available to render images. Its output is antialiased and better than dvips. If not available, the old dvips+convert chain will be used. (willu)
- Drop suggests on texlive-science, add suggests on dvipng.
- listdirectives: New plugin. (willu)
- filecheck: New plugin factoring out the PageSpec additions that were originally part of the attachment plugin.
- edittemplate: Don't wipe out edits on preview.
- color: New plugin from ptecza.
- autoindex: Avoid re-adding previously deleted (or renamed) pages.
I've produced a code_swarm visualization of the first 2+ years of ikiwiki's commit history.
[[!img Error: Image::Magick is not installed]]
PS, while I'm posting links to videos, here's a video of a lightning talk about ikiwiki.
--Joey
notes
Interesting things to watch for:
- Initial development of ikiwiki to the point it was getting web edits. (First 2 seconds of video!)
- Introduction to plugin support, and later, plugin changes dominating code changes.
- Introduction of openid support and the resulting swarm of openid commenters.
- Switch to git, my name in the logs changes from "joey" to "Joey Hess", and there are more code commits directly from others.
Getting the commit log was tricky because every web commit is in there too, so it has to deal with things like IPs and openids. The code swarm log.pl script will munge the log to handle these, and it was configured with code swarm.config.
Video editing by kino, ffmpeg, ffmpeg2theora, and too many hours of pain.
Audio by the Punch Brothers.
Ikiwiki in svn now has support for using OpenID, a decentralized authentication mechanism that allows you to have one login that you can use on a growing number of websites.
Traditional password-based logins are still supported, but I'm considering switching at least ikiwiki.info over to using only OpenID logins. That would mean blowing away all the currently registered users and their preferences. If you're active on this wiki, I suggest you log out and log back in, try out the OpenID signup process if you don't already have an OpenID, and see how OpenID works for you. And let me know your feelings about making such a switch. --Joey
[[!poll 59 "Accept only OpenID for logins" 18 "Accept only password logins" 35 "Accept both"]]
ikiwiki.info has upgraded to the not yet released ikiwiki 2.30. This version of ikiwiki drops support for subscribing to commit mail notifications for pages. The idea is that you can subscribe to the new RecentChanges feed instead. (Or create your own custom feed of only the changes you're interested in, and subscribe to that.)
So if you were subscribed to mail notifications on here, you'll need to change how you keep track of changes. Please let me know if there are any missing features in the RecentChanges feeds.
Statically building the RecentChanges also has performance implications, I'll keep an eye on server speed..
--Joey
I was asked a good question today: How can a company find someone to work on ikiwiki? To help answer this question, I've set up a consultants page. If you might be interested in being paid to work on ikiwiki, please add your information to the page. --Joey
And here's the first company looking for an ikiwiki developer that I am aware of:
The TOVA Company, a small medical software and hardware company in Portland, Oregon, is looking for developers to add functionality to ikiwiki. We're looking for developers who are already familiar with ikiwiki development, including plugins, and who would be willing to work on a part-time, non-employee, project-based basis for each of the small features that we want. The features we're interested in would obviously be GPL'd, and released to the community (if they'll have them
). Please contact Andrew Greenberg (andrew@thetovacompany) if you're interested. Thanks!
I've started using git as ikiwiki's main repository. See download for repository locations.
Note that all the sha1sums have changed from those in previously published git repositories. Blame git-svnimport.
I hope that this will make it easier to maintain and submit patches for ikiwiki.
--Joey
I've put together a short screencast that covers approximatly the first half of the setup document, and includes a demo of setting up a blog using ikiwiki.
http://kitenet.net/~joey/screencasts/ikiwiki_blog/
.. And now I've added a second screencast. Note that this uses a script that is only available in the as yet unreleased ikiwiki version 2.15.
http://kitenet.net/~joey/screencasts/ikiwiki_cgi_and_git/
--Joey
I've gone ahead and moved ikiwiki.info to the faster box mentioned on server speed. Most poll respondants felt the old box was fast enough, but it's getting a bit overloaded with other stuff.
If you can see this, you're seeing the new server. If not, your DNS server hasn't caught up yet. I'll keep the old server up for a while too and merge any changes across since git makes that bog-easy.
Please report any problems..
Ikiwiki now has an IRC channel: #ikiwiki
on irc.oftc.net
The channel features live commit messages for CIA for changes to both ikiwiki's code and this wiki. Plus occasional talk about ikiwiki.
Thanks to JoshTriplett for making this happen.
Google has accepted ikiwiki as a mentoring organization for Summer of Code 2007.
See our Summer of Code page for projects.
Commits to ikiwiki's source code are now fed into CIA, and can be browsed, subscribed to etc on its project page. Note that changes to the documentation wiki are currently excluded.
Some people may consider ikiwiki's default look to be a bit plain. Someone on slashdot even suggested perhaps it uses html 1.0. (Yes, an ikiwiki site has survived its first slashdotting. With static html, that's not very hard..) While the default style is indeed plain, there's more fine-tuning going on than you might think, and it's actually all done with xhtml and style sheets.
Stefano Zacchiroli came up with the idea of adding a css market page where IkiWikiUsers can share style sheets that you've come up with for ikiwiki. This is a great idea and I encourage those of you who have customised stylesheets to post them.
I'm also always looking for minimalistic yet refined additions to the default style sheet, and always appreciate suggestions for it.
--Joey
By the way, some other pages with RSS feeds about ikiwiki include plugins, TODO and bugs.