Sat 06 Oct 2018 11:16:53 PM -03

Current practice

Currently ikiwiki is adopted by the following reasons:

  1. There is a Debian package.
  2. It's flexible enough to support both local or remote side static compilation:
    • Local compilation by calling the ikiwiki command directly.
    • Remotelly by using a git hook.

When it's said both it means that you don't need to choose either of the two options: you can choose or both simultaneously.

Static site example

Here comes the mandadoty "Hello world" example from the statically generated site realm:

mkdir blog && cd blog
echo "Hello world..." > index.mdwn
ikiwiki --rebuild --exclude www . www

That's it! You have a generated site sitting at your www subfolder which can be copied remotelly using rsync.

Version control

It's a good pratice to keep your work under version control:

git init
echo "/.ikiwiki"       > .gitignore
echo "/recentchanges" >> .gitignore
echo "/www"           >> .gitignore
git add .
git commit -m "Initial import"

Add a bit of sofistication


Currently using Ikiwiki with Bootstrap:


You can create passwordless SSH keys and use rrsync (2) to restrict access. Then add an entry into your ~/.ssh/config:

Host blog
  User blog
  IdentityFile ~/.ssh/

Now simply run make web_deploy with the above mentioned Makefile do sync your static site!

Ikiwiki references